Any body know that this is possible?
I need some thing that will automatic update to current version or
automatic update from slackware 11 to slackware 12.

Condor <condor@stz-bg.com> wrote:
> Any body know that this is possible?
> I need some thing that will automatic update to current version or
> automatic update from slackware 11 to slackware 12.

If you need a near automatic update, we suggest windoze. Slackware
is a hobbyist distribution and manual updates are a high point in
the hobbyist's life.

cordially, as always,

rm

If you want to automatically track slackware-current that is possible using
slapt-get. It works well.

If you want to upgrade from 11 to 12 (when it's released) I suggest reading
the UPGRADE.TXT file that will be distributed with the release version.

As for the comment from the Windoze moron, forget him. With Slackware you
can upgrade major versions if you can read. No one in their right mind
suggests that upgrading from one major Windows version to the next is wise.
It's always reinstall the new version.

I've been upgrading my Slackware box since it was installed with 8.1.


"Condor" <condor@stz-bg.com> wrote in message
news:1175755564.956403.286110@y80g2000hsf.googlegr oups.com...
> Any body know that this is possible?
> I need some thing that will automatic update to current version or
> automatic update from slackware 11 to slackware 12.
>

On Thu, 4 Apr 2007, Condor wrote:



> Subject(!): Automatic update from Slackware 11 to current or 12?
>
> Any body know that this is possible?
> I need some thing that will automatic update to current version or

You can try slackpkg (configure it to upgrade to "Slackware current" or
"Slackware 11"), it upgrades OK.

> automatic update from slackware 11 to slackware 12.

Slackware 12 is not released.

PW

Condor <condor@stz-bg.com> wrote:
>Any body know that this is possible?
>I need some thing that will automatic update to current version or
>automatic update from slackware 11 to slackware 12.

I understand slapt-get is supposed to do this, but I've never been gutsy
enough to try it. (You're going to have to fix up your conf files
in any case.)

Swaret is a similar program, IIRC.

There was another tool called autoslack--I'm pretty sure it's not being
worked on anymore.

(Caveat: I haven't checked the dev status of any of these tools in a
long time, nor have I used any of them on a consistent basis.)

-Beej

Condor wrote:

> Any body know that this is possible?
> I need some thing that will automatic update to current version
> or automatic update from slackware 11 to slackware 12.

Sure, but read the Changes_and_Hints.txt, and UPGRADE.txt since
slack current includes some major changes to the file system
layout, new packages and splitting of packages into new
locations. Tools for automatic upgrading are slackpkg, swaret and
slapt-get. Swaret is currently looking for a new maintainer, but
proved to be very reliable in the past and has the best package
exclude feature. Slapt-get is a frontend to pkgtools and provides
a lot of options. The --dist-upgrade option is a good way to make
sure that all base packages required by a new slack version will
be installed. Currently I'm using slackpkg, it's the native
package tool for slackware. IMO the dialog interface provides the
best control over the installation process.

All tools need some configuration, but correctly configured they
make updates very easy.

HTH
Joerg
--
For email use g m x d o t n e t

On 2007-04-05, Joerg <jstadermann@see_signature.net> wrote:
>
> Sure, but read the Changes_and_Hints.txt, and UPGRADE.txt since
> slack current includes some major changes to the file system
> layout, new packages and splitting of packages into new
> locations.


Yes, very good advice. At the moment, UPGRADE.TXT is a link to
CHANGES_AND_HINTS.TXT in the -current tree, as the information
needed for an upgrade to -current is covered in C&H.


> Tools for automatic upgrading are slackpkg, swaret and slapt-get.
> Swaret is currently looking for a new maintainer, but proved to
> be very reliable in the past and has the best package exclude feature.


Wow. Apparently I've been reading different forums and IRC channels
than you have. The term "reliable" is not one that I have associated
with swaret. [1]


> Slapt-get is a frontend to pkgtools and provides a lot of options.
> The --dist-upgrade option is a good way to make sure that all base
> packages required by a new slack version will be installed.


Yeah, that makes sure all of the A series is installed. Granted,
that might ensure that you have a bootable system, but that's not
worth a crap when apache stops working due to the missing mm package
from the L series (which was the case in an upgrade from 10.2 to
11.0).


> Currently I'm using slackpkg, it's the native package tool <SNIP>


Um, no, it's not. Slackware's native package manager is the suite
of things included with pkgtool(8) - installpkg(8), removepkg(8),
upgradepkg(8), explodepkg(8), and makepkg(8).

One *big* advantage of slackpkg is the fact that it will syncronize
your system's installed packages with the official packages present
on whatever mirror you selected.

If I had to choose an automated tool to recommend, it would most
definitely be slackpkg. The maintainer of slackpkg is a frequent
contributor to Slackware - grep the ChangeLogs for PiterPunk
That being said, the footnote below applies to it just as it does
to any of the others.


[1] I'd guess that a fair amount of the errors that people encounter
when using *any* automatic upgrade tool are due to PEBKAC. It
seems that the best way to keep information undiscovered is to
place it in a manual page or a file named README.

RW

Robby Workman wrote:

> On 2007-04-05, Joerg <jstadermann@see_signature.net> wrote:
<snip>

>>
>> Tools for automatic upgrading are slackpkg, swaret and
>> slapt-get. Swaret is currently looking for a new maintainer,
>> but proved to be very reliable in the past and has the best
>> package exclude feature.
>
>
> Wow. Apparently I've been reading different forums and IRC
> channels
> than you have. The term "reliable" is not one that I have
> associated with swaret. [1]
>
>

Why reading, I' ve been using it until recently and it it did a
good job. It's only because of the open maintenence issue that
I'm looking into alternatives.

<snip>

Joerg
--
For email use g m x d o t n e t

Joerg wrote :

> Why reading, I' ve been using it until recently and it it did a
> good job.

Then you are more lucky than many others.

There's a reason for Robby's comment and that is we've seen quite a
number of people coming to this group with a cry for help because their
use of swaret has left them with a totally FUBAR'red slackbox.
--
Thomas O.

This area is designed to become quite warm during normal operation.