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.
Does Slackware have an updating feature like Gentoo, Fedora Core, SUSE, etc? By updating feature I mean something that can update outdated applications on your system. I haven't really seen anything indictating anything yet.
If there isn't any feature to update what way would I go about doing this?
I plan to install Slackware next weekend hopefully so need to get this out before .
CrEsPo, keep in mind that none of those tools suggested by kodon are official slackware tools... they are all third-party...
the official way to keep your slackware up to date is by monitoring the changelog at http://www.slackware.com/changelog (or in your relevant FTP dir) and/or subscribing to the slackware security mailing list...
this way, whenever there is a patch released, you just download it and then do an "upgradepkg" on it...
win32sux: Thanks for the information. Yeah I could always do it that way, but I'm a lazy so I tend to update weekly. If I find the other ways to be not so well I'd probably do it that way. I think I may subscribe though, just so I get notified as I tend to have a bad memory .
datadriven: I'd be happy to try out your program once I install Slackware .
I think using slackpkg is a good middle ground. You review the changlogs then use slackpkg to upgrade each package. That way you know exactly what is being done, you see it being done. You know if something is supposed to be removed. You know if changes to a config needs to be done. The people that seem to get in trouble with swaret and slapt-get just allow them to do their thing without being involved in the process. This is not Debian. The distro is not built with package management and dependency checking in mind. Therefor the updaters can never equal apt-get.
i use slackpkg...like ringwraith says...if you keep your eye on the changelog, you know what you need to upgrade and what it will do...i just brought 10.1 up to current almost flawlessly....(i had to go back in install cyrus, which fixed the only problem i ran into)
Originally posted by win32sux CrEsPo, keep in mind that none of those tools suggested by kodon are official slackware tools... they are all third-party...
and Pat V. does not support using swaret at all..........
I use slackpkg to download and install the patches and apps I need and to upgrade when needed.
I only use swaret for installing 3rd party software that there is no official Slack package for, but with a great deal of caution. I would never trust swaret to do a system update or upgrade.
You may consider yourself "lazy" but which will require less effort, reading the changelogs and installing the patches as needed, or reinstalling the whole system because some "tool" borked it for you?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.