[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
talk:slackware:beginners_guide [2017/11/05 21:46 (UTC)] – [Installing updates using slackpkg] alienbobtalk:slackware:beginners_guide [2017/11/06 10:18 (UTC)] (current) – [Installing updates using slackpkg] bormant
Line 222: Line 222:
  
 ====== Installing updates using slackpkg ====== ====== Installing updates using slackpkg ======
-<code>slackpkg install-new</code> +>><code>slackpkg install-new</code> installs NEW packages marked with "Added" in ChangeLog.txt, so it only suitable to 1) upgrade between releases (for ex. 14.1 to 14.2) or to 2) update current. This do nothing to update stable release version that doesn't get any NEW packages, only /patches/*.
-> installs NEW packages marked with "Added" in ChangeLog.txt, so it only suitable to 1) upgrade between releases (for ex. 14.1 to 14.2) or to 2) update current. This do nothing to update stable release version that doesn't get any NEW packages, only /patches/*.+
  
-> For slackpkg ''update'', ''install-new'', ''upgrade-all'', ''clean-system'' sequence the ''install-new'' and ''clean-system'' are odd and useless on stable release . \\ --- //[[wiki:user:bormant|Serg Bormant]] 2017/11/05 11:40 (UTC)//+>> For slackpkg ''update'', ''install-new'', ''upgrade-all'', ''clean-system'' sequence the ''install-new'' and ''clean-system'' are odd and useless on stable release . \\ --- //[[wiki:user:bormant|Serg Bormant]] 2017/11/05 11:40 (UTC)//
  
-That is not correct, as history proves. Sometimes, a package gets added as a "patch" after release-date, and then "''slackpkg install-new''" is needed. From the Slackware 13.37 ChangeLog.txt: <code>+>That is not correct, as history proves. Sometimes, a package gets added as a "patch" after release-date, and then "''slackpkg install-new''" is needed. From the Slackware 13.37 ChangeLog.txt: <code>
 +--------------------------+ +--------------------------+
 Sat Mar 16 07:10:09 UTC 2013 Sat Mar 16 07:10:09 UTC 2013
Line 233: Line 232:
   This is needed for Psych (YAML wrapper) in the new Ruby package.   This is needed for Psych (YAML wrapper) in the new Ruby package.
 </code> \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2017/11/05 21:42 (UTC)// </code> \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2017/11/05 21:42 (UTC)//
 +
 +Yes, since 8.1 (first release with versioned packages) it was only tree times by two reasons:<code>
 +9.1: patches/packages/kernel-headers-2.4.24-i386-1.tgz:  Added.
 +
 +13.1: patches/packages/libyaml-0.1.4-i486-1_slack13.1.txz:  Added.
 +13.37: patches/packages/libyaml-0.1.4-i486-1_slack13.37.txz:  Added.
 +</code>
 +Readind ChangeLog.txt can help to discover this rare case and launch ''slackpkg install libyaml'' if needed. But if skip some series on install she will be prompted to install NEW (Added) package on //every// ''slackpkg install-new'' run (yes, blacklist can help and partial install is not supported :) ).\\
 + --- //[[wiki:user:bormant|Serg Bormant]] 2017/11/06 09:33 (UTC)//

Trace:

talk:slackware:beginners_guide ()