[SOLVED] What is the difference between -current and 13.0?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was trying to learn how to keep my Slackware 13.0 up-to-date, then I noticed there are these two types of mirrors I have to choose. If 13.0 is the latest, what is the difference?
I just changed the mirror in /etc/slackpkg/mirrors from a 13.0 to a -current server, and now I have many updates...
Another problem, when I tried to "slackpkg update" then "slackpkg check-updates" in both cases, it returned: "No news is good news"... Yet, when I used "slackpkg upgrade-all", there WERE packages to be upgraded... WHat is the purpose of "check-updates"?
Thanks in advance!
Click here to see the post LQ members have rated as the most helpful post in this thread.
I thought that ChangeLog would contain ALL changes to the packages... I think I got it now.
So I also need to use install-new to get the newer packages...
Thanks for the info!
Close, but not quite right.
First you would use "slackpkg update" to download the latest version of the Changelog to your Slackware box.
Then you would use "slackpkg upgrade-all" to have slackpkg upgrade any packages, that you currently have installed, to their latest version in the Changelog. The "upgrade-all" option does not install newly created packages listed in the Changelog.
You would then use "slackpkg install-new" to install any new packages mentioned in the Changelog.
Not positive as to sequence, but pretty sure "slackpkg install-new" would come before "slackpkg upgrade-all". Can any one validate this?
Originally Posted by Alien Bob
Slackware does not care about order of installation.
To be a bit pedantic, 'install-new' *should* come before 'upgrade-all' as a matter of practice.
As an example, let's consider the tcpdump package. It's presently built in such a way that you get the tcpdump binaries *and* the libpcap libraries. If, for whatever reason, libpcap were split out into a separate package, and you just did 'upgrade-all' without first doing 'install-new', you'd be missing the libpcap shared library, and tcpdump would therefore refuse to run.
In this particular case, it's not an issue, because the system doesn't need tcpdump to boot and/or to continue running properly; however, it shouldn't be too difficult to imagine a case where it *would* cause a problem.
I don't think it would be a problem if you run install-new later. If you forget to run install-new then it could be a problem next time you boot. However, as you mentioned it's a better practice, hence I edited my post.
I don't think it would be a problem if you run install-new later. If you forget to run install-new then it could be a problem next time you boot.
It *can* be a problem before that even. Here's an entirely contrived example, but it works:
Let's pretend bash requires libbash, which is presently included in the bash package.
Now let's pretend libbash is split out into a separate package in the last batch of updates.
Now let's pretend you did 'upgrade-all' without first doing 'install-new'
Now let's accidentally close our terminal window.
Assuming your window manager has a "run" dialog (e.g. Alt F2), you can invoke "xterm -e /bin/ksh" from that to recover, but you get the idea, right? :-)
Perhaps not quite so contrived example from recent history was the release of the xz package so that the new .txz format could be supported.
The xz package was released Tue Apr 7 20:12:35 CDT 2009 and the first packages using .txz were released Fri May 8 18:49:03 CDT 2009 ( http://www.nielshorn.net/slackware/_...geLog_13.0.txt - Thanks Niels!). You would not have wanted to be away for a month without running install-new first!