Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
06-10-2004, 05:17 PM
|
#1
|
|
LQ Newbie
Registered: Apr 2004
Location: France
Distribution: Debian
Posts: 16
Rep:
|
swaret or slackpkg ?
Hello
I'm searching for THE tool to upgrade my slack.
swaret was included in slack 9.1 (extra) and slack-pkg is included in current.
Swaret has been removed from current/extra...
Swaret seems to be a good tool, with more usefull feature than slack-pkg...
Is there a reason why Pat removed that tool ?
It doesn't seem to be deprecated !
Fred
|
|
|
|
06-10-2004, 07:08 PM
|
#2
|
|
Senior Member
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,506
Rep: 
|
Yes, why?
Did swaret cause too much trouble?
gargamel
|
|
|
|
06-10-2004, 07:15 PM
|
#3
|
|
Member
Registered: Jul 2003
Location: Göteborg
Distribution: Arch Linux (current)
Posts: 553
Rep:
|
The ChangeLog doesn't say anything about removing swaret, which is a bit odd.
Anyway, as to THE tool to upgrade Slack: I haven't tried slackpkg, but I'm a big fan of swaret - working like a charm 
Last edited by Bebo; 06-11-2004 at 08:29 AM.
|
|
|
|
06-10-2004, 07:18 PM
|
#4
|
|
Senior Member
Registered: Sep 2003
Location: Indiana
Distribution: Slackware-current
Posts: 1,244
Rep:
|
If you search the board, this has been discussed. Swaret was also suspended from freshmeat (?) for a time. That was a about the same time Pat dropped it from current so one would assume..... It had to do with a lot of immature behavior by the developer and some of his minions.
I recommed updating with the current changelog, wget and upgradepkg. Look at the board at all the problems people report with swaret. I think most of the time it is user error because they don't understand what swaret is doing and what needs to be done.
|
|
|
|
06-11-2004, 08:03 AM
|
#5
|
|
Member
Registered: Jul 2003
Location: Virginia
Distribution: Ubuntu Hoary (5.04)
Posts: 550
Rep:
|
Quote:
|
I think most of the time it is user error because they don't understand what swaret is doing and what needs to be done.
|
Here, here! SWareT's not a bad tool if you use it correctly. Check the Slackware ChangeLog before upgrading with SWareT and you can see what you need upgraded, what you can ignore, and what special steps you might need to take before/after upgrading. SWareT is nice, but I recommend not doing below
Code:
swaret --upgrade -a
|
|
|
|
06-11-2004, 10:14 AM
|
#6
|
|
Member
Registered: Aug 2003
Posts: 83
Rep:
|
I personally use slapt-get to keep up to date with -current, but heed ringwraith's words. My typical upgrade procedure is as follows:
1) Check the ChangeLog on Slackware.com. Note any packages removed, retired to /pasture, or added. Also a good place for the latest news on future plans for the distribution including releases, etc.
2) Run slapt-get --update && slapt-get --upgrade to upgrade to new versions of packages.
3) Run removepkg on any removed/retired packages.
4) Run slapt-get --install on any new packages that I want.
5) cd /etc && find . -name "*.new" and merge in any appropriate changes.
6) Test things out to make sure it all works.
Skip one of those steps and you're asking for trouble. Sometimes packages are split up, or combined, or new required libraries are added (especially during major upgrades to GNOME) and unless you add these packages your software will not run properly.
Last edited by Toth; 06-11-2004 at 10:17 AM.
|
|
|
|
06-11-2004, 10:21 AM
|
#7
|
|
Member
Registered: Jul 2003
Location: Göteborg
Distribution: Arch Linux (current)
Posts: 553
Rep:
|
I for one do swaret --update and swaret --upgrade, usually answering to upgrade [A]ll. (I've never dared use the -a option when I upgrade, though.) And every once in a while I do a swaret --dep. No problems whatsoever. I've even managed to root out Dropline twice using only swaret (somewhat assisted by removepkg on one occasion).
|
|
|
|
06-11-2004, 11:09 AM
|
#8
|
|
Member
Registered: Feb 2004
Location: FRG, EU
Distribution: Slackware current
Posts: 51
Rep:
|
Quote:
Originally posted by Toth
Skip one of those steps and you're asking for trouble.
|
I also always switch to init 3 before upgrading stuff like X, GTK, KDE, Gnome, ... I do it exactly like Toth, except that I use Swaret. The only thing that bothers me about Swaret is that it is so slow at listing upgradeable packages. But I still use it because slapt-get --upgrade isn't as verbose as swaret --upgrade.
|
|
|
|
06-11-2004, 01:08 PM
|
#9
|
|
Member
Registered: Feb 2003
Location: Richmond VA
Distribution: Slackware 11 -- CentOS 4.4
Posts: 115
Rep:
|
Regarding slapt-get and verboseness...
Quote:
|
But I still use it because slapt-get --upgrade isn't as verbose as swaret --upgrade.
|
slapt-get has the -S (--show-stats) option that "will show curl style
download information." (FAQ) ... dunno if that's what swaret does (never used it).
Just a note for first time slapt-get --upgrade runs (like mine this week). If you run via
sudo'd user be sure /sbin in in that user's $PATH -
else the subsequent updatepkg et. al. will fail,
forcing manual updates of all (yes I learned this the hard way though it's in the FAQ  )
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 06:34 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|