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 did that on my 14.1 system (my printer needed a newer hplip). I just took the -current source directory for hplip, ran the SlackBuild, and did an upgradepkg on the package that it generates. Works nicely. You can get all the files to do that from the Slackware64-current source tree (any mirror, it's under source/ap/hplip). Btw, just installing the -current package on 14.1 didn't work for me, and I think it's better to just compile it for your system anyway.
Yes, need to recompile : there're huge differences between 14.1 and actual current. Packages are build against libs that might not be included or other versions. Installing those might even break your system.
Did you think 14.1 was the latest stable release, or something like that?
No, no, no. 14.1 is 2.5 years old -- my 2015 laptop couldn't run it. The latest normal version is -current. I believe it will simply get renamed to 14.2 --- soon.
Did you think 14.1 was the latest stable release, or something like that?
No, no, no. 14.1 is 2.5 years old -- my 2015 laptop couldn't run it. The latest normal version is -current. I believe it will simply get renamed to 14.2 --- soon.
That your recent laptop can't run 14.1 doesn't make it obsolete for everyone. All depends on the target machine and the intended usage by the original poster, of which we know very few.
Furthermore there are cases where just upgrading the kernel or some components of the system suffice: your mileage may vary.
14.1 is the latest stable release and will stay so until 14.2 be released.
Oh, and while I am in a picky mood and before moving to do something more constructive that these comments: I don't know what is a normal version, only that -current is by definition not a stable one. Actually it is not a version at all.
Have a good day.
Last edited by Didier Spaier; 05-31-2016 at 09:13 AM.
Reason: s/mode/mood/
I totally agree with Didier. What follows is additional clarification on the quoted text below.
Quote:
Originally Posted by Didier Spaier
Oh, and while I am in a picky mood and before moving to do something more constructive that these comments: I don't know what is a normal version, only that -current is by definition not a stable one. Actually it is not a version at all.
The issue is the label. Current is technically an unstable branch. It can (and occasionally does) break things and cause a ruckus. However, Pat and team do a ton of work to minimize those types of problems to their users, so most of those wrinkles are ironed out long before it ever reaches the mirrors. This causes a lot of users to throw the "stable" label around regarding -current. And most of the time, they're right. It tends to be stable... until it isn't.
The official stable releases with Slackware (currently the latest being 14.1) prevent changing things that will impact the whole OS, like upgrading a library that has it fingers in a lot of programs, like the switch from libjpeg-v8a to libjpeg-turbo. When things like that are updated, Pat and team need to recompile a lot of packages that rely on that. Then, when all of those are pushed out to the mirrors, it will break all your 3rd party packages that rely on that. Those types of things happen semi-frequently on -current (until you get towards the end of the development cycle, like we are right now). They won't happen in an actual stable release.
Unfortunately, with the long period between 14.1 and the soon to be released 14.2, many users have needed to go to -current to properly support their hardware, me included. But, even if -current usually runs without issues, it should NOT be considered a stable release. Once it has been put through enough checks and passes them, Pat will release it as the next stable, 14.2. Until then, -current should be considered potentially unstable, even if it runs well right now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.