LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 12-18-2009, 10:51 AM   #1
Geriao
Member
 
Registered: Dec 2009
Distribution: Ubuntu Karmic Koala, Slackware 13.0
Posts: 66

Rep: Reputation: 16
What is the difference between -current and 13.0?


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.
Old 12-18-2009, 10:59 AM   #2
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
-current is the development branch of Slackware Linux, which goes through testing and gets incorporated in the next version of Slackware.
-stable is the released branch,which is 13.0 presently.

Important Info:
http://www.slackware.com/faq/do_faq.php?faq=general#5
http://www.slackware.com/changelog/

Regards

Last edited by ~sHyLoCk~; 12-18-2009 at 11:02 AM.
 
1 members found this post helpful.
Old 12-18-2009, 11:59 AM   #3
Geriao
Member
 
Registered: Dec 2009
Distribution: Ubuntu Karmic Koala, Slackware 13.0
Posts: 66

Original Poster
Rep: Reputation: 16
Thanks for the explanation, ~sHyLoCk~! I was trying to find this information on the mirrors, but couldn't...

Also, what about the check-updates option in slackpkg? Why didn't it show me there were packages to be updated?
 
Old 12-18-2009, 12:25 PM   #4
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
From man page:

update:
The "update" action will download and format the list of files and packages in Slackware. Every time this list is changed, the update need to be run.

check-updates:
Verify if there is any update to ChangeLog.txt.

If there's no update to Changelog.txt, you get the message you go in your first post.

Quote:
Also, what about the check-updates option in slackpkg? Why didn't it show me there were packages to be updated?
First make a choice, which branch will you follow. Stable or Current. Then uncomment one mirror from you /etc/slackpkg/mirrors

Then re-run:
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
If you get any error messages please post them here.

Regards

Last edited by ~sHyLoCk~; 12-18-2009 at 10:31 PM.
 
2 members found this post helpful.
Old 12-18-2009, 05:58 PM   #5
Geriao
Member
 
Registered: Dec 2009
Distribution: Ubuntu Karmic Koala, Slackware 13.0
Posts: 66

Original Poster
Rep: Reputation: 16
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!
 
Old 12-18-2009, 06:27 PM   #6
regis_n_bits
Member
 
Registered: Mar 2006
Distribution: Slackware64 14.1 (kernel 3.14.4)
Posts: 83

Rep: Reputation: Disabled
Quote:
Originally Posted by Geriao View Post
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.
 
Old 12-18-2009, 09:00 PM   #7
zbreaker
Member
 
Registered: Dec 2008
Location: New York
Distribution: Slack -current, #!, vsido
Posts: 228

Rep: Reputation: 29
Not positive as to sequence, but pretty sure "slackpkg install-new" would come before "slackpkg upgrade-all". Can any one validate this?
 
Old 12-18-2009, 09:04 PM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,379

Rep: Reputation: Disabled
Quote:
Originally Posted by zbreaker View Post
Not positive as to sequence, but pretty sure "slackpkg install-new" would come before "slackpkg upgrade-all". Can any one validate this?
Slackware does not care about order of installation.

Eric
 
Old 12-18-2009, 10:18 PM   #9
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,944

Rep: Reputation: Disabled
Quote:
Originally Posted by zbreaker View Post
Not positive as to sequence, but pretty sure "slackpkg install-new" would come before "slackpkg upgrade-all". Can any one validate this?
Quote:
Originally Posted by Alien Bob View Post
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.
 
1 members found this post helpful.
Old 12-18-2009, 10:30 PM   #10
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Thanks Robby,
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.

Regards
 
Old 12-18-2009, 11:29 PM   #11
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,944

Rep: Reputation: Disabled
Quote:
Originally Posted by ~sHyLoCk~ View Post
Thanks Robby,
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.
Oops. :-)

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? :-)
 
1 members found this post helpful.
Old 12-19-2009, 10:04 AM   #12
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,517

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
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!

Last edited by allend; 12-19-2009 at 10:14 AM.
 
  


Reply

Tags
slackpkg, update, upgrade


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
shell script to find the difference betwwn two file and place the difference to other kittunot4u Linux - General 3 07-19-2010 05:26 AM
cvs diff the most current and second last current version powah Linux - Software 1 03-30-2006 02:02 PM
Difference between 10.1 and current distro? moffen Slackware 4 05-18-2005 10:58 PM
difference between fget(fd) and current->files->fd[fd] appas Programming 3 08-09-2004 11:46 AM
current Slack-Current giving troubles? r_jensen11 Slackware 5 02-02-2004 06:08 PM


All times are GMT -5. The time now is 03:04 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration