In Linux Slackware Project how do I update Slack 12 following the "Changelogs" route?
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.
In Linux Slackware Project how do I update Slack 12 following the "Changelogs" route?
In Linux Slackware Project, how do I update Slack 12 following the "Changelogs" route? When I clicked on CL all I got was an entry into all of the text files; very interesting, but no explanation about downloading.
I've only ever used the update and upgrade-all options for keeping 12.0 up to date. Isn't the install-new option more for installing new packages rather than updating those already installed?
I've only ever used the update and upgrade-all options for keeping 12.0 up to date. Isn't the install-new option more for installing new packages rather than updating those already installed?
The "install-new" option will prompt you to install things that were *added* to Slackware -- it doesn't prompt you to install everything you don't already have installed. Without going into great detail, it does some regex parsing of the ChangeLog and checks another file that PiterPunk notes stuff which was added without the relevant regex in the ChangeLog.
The "install-new" option is normally needed only when you're upgrading from one Slackware release to another - that way, you don't miss out on installing any packages that were added during the -current cycle. However, it's a good idea to make a habit of always running it just in case; the best example which illustrates this point is the addition of mozilla-nss to slackware-11.0/patches/ back some time ago. Lots of users never installed that new package, and since the gaim package released at the same time required it for encryption, gaim was broken. This led to the big fiasco with the gaim/pidgin developers... :/
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.