SlackwareThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What I normally do is that I don't use swaret immediatly off the net but I Rsync slackware-current tree and then use swaret of a local repository.
That way I can create CD's for people who cannot use swaret to update because of a slow connection.
Mine is not fast either but it's constant and that's enough for me.
if there are new packages included in Slack-current or 10, swaret won't pick up on this when you use swaret --upgrade -a. You will have to install these new packages, again you can use swaret for this. Also if packages are sent to pasture swaret won't pick this up. You have to remove them yourself.
I'll be gettin the cd's and keeping up2date using swaret, best way really.
I don't really think -current is for me, I'm happier compiling stuff if I want to upgrade rather than constatly upgrading stuff I don't care about - when I am gonna use KDE or GNOME?.
I've seen waaaay to many problems in the forums about swaret etc and franky, for a main home or office pc, I just don't think it's worth it.
Originally posted by SBing I'm happier compiling stuff if I want to upgrade rather than constatly upgrading stuff I don't care about - when I am gonna use KDE or GNOME?.
Ehm.. just FYI... If you haven't installed certain packages, swaret won't
update them. Kind of what updating is about isn't it? :-)
Ehr, no - I would have them installed but I wouldn't use them particularly often :) That's what's on most machines in the office - GNOME/KDE is there if people want it but they don't get updated. If there is a way to stop swaret updating them then it'd be okay.
Originally posted by SBing If there is a way to stop swaret updating them then it'd be okay.
Satisfied ?
Steve
Well... actually... there IS a way... you can use the EXCLUDE thingy in the swaret.conf... Normally it allready excludes kernel and lilo packages if I can recall...
look at this link (nr 23 and 24) for examples.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.