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.
I've never used Slapt-get. I WAS happy with swaret, but my latest upgrade borked KDE! Apparently it missed a library and I had to grab it manually from slackware.com. Does stuff like that happen with slapt-get?
swaret upgrades what is already on your system. It will not install a new or re-named package unless you tell it to and the only way to know that is to read the change logs.
swaret --update This updates the database comparing what is already installed to what is new
swaret --upgrade -a This upgrades all "installed" packages that have an upgrade available
If after reading the change log, there is a an addition that will be new to the system the following needs to be done.
swaret --get foo
swaret --install foo
swaret is not the problem. The problem is that people don't realize that it has limitations that require an administrator's intervention.
Renamed packages cause the same problem by the way.
note: I don't use swaret, but I think I'm pretty close on the commands - if I'm off please correct
I have never used slapt-get. I do use swaret from time to time.
It's automation makes trivial things less time consuming.
I find on the major stuff it usually messes up.
It breaks important things. However, it's nothing that can't easily be fixed if you know how.
If you don't know already howto do it manually, learn before relying on swaret.
Although personally I use swaret, but honestly, any difference between the two tools are negligible.
And also, if used correctly... neither of them will give you any major problems. Common problems faced by using these tools are usually self inflicted anyway.
eg. Updating libs/apps that are in use. Failure to migrate to updated config files , etc. etc.
One useful tip: Avoid updating within X, especially when there are major updates to core libs... and a reboot after that might not hurt either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.