LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-25-2016, 10:25 PM   #1
tb75252
Member
 
Registered: Oct 2010
Posts: 167

Rep: Reputation: Disabled
Package from slackware64-current


I installed Slackware 14.1, 64-bit.

I noticed that slackware64-current has a more recent hplip package (available at http://ftp.slackware.com/pub/slackwa...lackware64/ap/)

Can I install that package to my 14.1 version? How?
 
Old 05-26-2016, 01:20 AM   #2
drgibbon
Member
 
Registered: Nov 2014
Distribution: Slackware64 14.2
Posts: 497

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
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.

Last edited by drgibbon; 05-26-2016 at 01:21 AM.
 
3 members found this post helpful.
Old 05-26-2016, 06:02 AM   #3
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 515
Blog Entries: 3

Rep: Reputation: 139Reputation: 139
Package from slackware64-current

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.
 
2 members found this post helpful.
Old 05-30-2016, 10:55 PM   #4
colinh2
Member
 
Registered: Dec 2015
Posts: 31

Rep: Reputation: Disabled
Quote:
Originally Posted by tb75252 View Post
I installed Slackware 14.1, 64-bit.
Yes, I made that mistake too :-)

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.
 
Old 05-31-2016, 04:32 AM   #5
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,001

Rep: Reputation: Disabled
Quote:
Originally Posted by colinh2 View Post
Yes, I made that mistake too :-)

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/
 
1 members found this post helpful.
Old 05-31-2016, 01:24 PM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,185

Rep: Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924Reputation: 3924
I totally agree with Didier. What follows is additional clarification on the quoted text below.

Quote:
Originally Posted by Didier Spaier View Post
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.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
llvm-config problem in slackware64-current LLVM 3.2 package teeemcee Slackware 0 01-24-2013 02:44 PM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Slackware64 -current No Sound mlpa Slackware 1 03-07-2010 03:02 PM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
Slackware64-current on a second HD. glore2002 Slackware 7 08-23-2009 11:38 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:22 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration