LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Question regarding update tools (https://www.linuxquestions.org/questions/slackware-14/question-regarding-update-tools-494134/)

Ruhar 10-20-2006 10:31 AM
Question regarding update tools
 
Hi there, I've been using Slack for a little while now but have never looked at any of the upgrading tools out there (slackpkg, swaret, slapt-get, etc.) I've always simply used wget to upgrade patches only. However, I may consider staying current at this point and follow the dev tree. Can you guys give me your opions of which you prefer?

Thanks!

Okie 10-20-2006 11:07 AM
i use slapt-get to download & install patches for slackware

Hangdog42 10-20-2006 12:38 PM
Automating the download is one thing, but automating the install, particularly off of current, is probably not a bright idea. There are LOTS of threads here where people used swaret, slapt-get, etc. to keep current with current, only to find that some packages bork their system. Some packages require configuration changes, and none of the automated programs do that. Do yourself a favor, if you need to use something like swaret or slapt-get, only use after reading the changelog.

Sonneteer 10-20-2006 01:18 PM
When following current with things like slapt-get, if a package gets reverted back to a previous version, you'll still have to do it manually, since update tools won't "downgrade" automatically (Patrick mentions this in the "Welcome to Linux (Slackware 11.0)" email (in the aaa_base package)).

I used slapt-get to stay with current from 10.2 to 11.0 (I found slapt-get to be faster than swaret, but I haven't tried slackpkg). So long as you keep an eye on the changelog for package roll backs, splits, merges, removals, renaming, and new additions, everything should go fine.

Okie 10-20-2006 01:47 PM
i agree with Sonneteer, stay out of Current if you want to keep a stable & usable system, Current is for Patrick V. and his friends/developers to use for testing & building the next release so packages in there can break things so stick with release # 11 for now...

MS3FGX 10-20-2006 04:32 PM
I have only very rarely had issues following --current. If you read the changelog, there is very little that can go wrong. If something is that broken, Pat wouldn't put it out there in the first place, even in --current.

Quote:
When following current with things like slapt-get, if a package gets reverted back to a previous version, you'll still have to do it manually, since update tools won't "downgrade" automatically (Patrick mentions this in the "Welcome to Linux (Slackware 11.0)" email (in the aaa_base package)).
Has this ever actually happened though? I get what he means, and it certainly would be a problem, but I don't actually recall him dropping back to an older version in --current, he would rather build a new one that fixes whatever the problem was and then increment the build number in the package name, which slapt-get will pick up on (not sure about others).

In either event though, automated or not, you should always be reading the changelog.

Alien Bob 10-20-2006 05:03 PM
Quote:
Originally Posted by MS3FGX
I have only very rarely had issues following --current. If you read the changelog, there is very little that can go wrong. If something is that broken, Pat wouldn't put it out there in the first place, even in --current.



Has this ever actually happened though? I get what he means, and it certainly would be a problem, but I don't actually recall him dropping back to an older version in --current, he would rather build a new one that fixes whatever the problem was and then increment the build number in the package name, which slapt-get will pick up on (not sure about others).

In either event though, automated or not, you should always be reading the changelog.
Packages in -current (between 10.2 and 11.0) that were reverted to lower versions: cups, imagemagick, lilo, mysql, e2fsprogs.

Eric

MS3FGX 10-20-2006 06:41 PM
Ah, out of those I only have lilo, so I didn't notice.


All times are GMT -5. The time now is 09:22 AM.