[2025-jun-17] The SlackDocs mailing lists at https://lists.alienbase.nl/mailman/listinfo have been retired. No one has been using these lists for years and it's time to say goodbye. The list archives remain available at https://scalzi.slackware.nl/mailman/listinfo/slackdocs

[2025-jun-17] The SlackDocs Wiki has moved to a new server, in order to make it more performant.

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
slackware:slackpkg [2012/09/10 15:23 (UTC)] – [install] cmysterslackware:slackpkg [2023/05/12 08:53 (UTC)] (current) – mozes
Line 1: Line 1:
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
 ====== slackpkg ====== ====== slackpkg ======
-Slackpkg is an automated tool to manage local packages and to install new package over a network. Nowadays slackpkg comes as part of Slackware, but if you do not have it installed, the latest version can be downloaded from [[http://sourceforge.net/projects/slackpkg/files/latest/download|SourceForge]] and installed with installpkg.+ 
 +Slackpkg is an automated tool to manage local packages and to install new package over a network. slackpkg is found within the 'ap' (Application) series of Slackware and will be installed by default.
  
 ===== Configuring ===== ===== Configuring =====
  
-Before slackpkg can be used it needs to have a current list of packages and their versions and that can be downloaded automatically by the tool itself once a mirror site is selected. To select a mirror, just uncomment a single URL in the file ''/etc/slackpkg/mirrors''. Note that the links are sorted by Slackware release versions so make sure that the selected link is in the same release that you are interested in.+ 
 +=== Initial Setup === 
 + 
 +Before slackpkg can be used it needs to have a current list of packages and their versions and that can be downloaded automatically by the tool itself once a mirror site is selected.  
 + 
 +To select a mirror, just uncomment a single URL in the file ''/etc/slackpkg/mirrors''. 
 + 
 +<note tip>The links are sorted by Slackware release versions so make sure that the selected link is in the same release that you are interested in. It is recommended, though not required, that you use the ''mirrors.slackware.com'' mirror, as that one will automatically redirect you to your geographically closest mirror.</note> 
 + 
 +<note important>mirrors.slackware.com does not support the ARM/AArch64 platform</note> 
  
 Then run: Then run:
Line 20: Line 30:
      
 Otherwise slackpkg will download and install the current package information and will use that list.\\ Otherwise slackpkg will download and install the current package information and will use that list.\\
 +
 +
 +<note tip>If you have installed Slackware -current (the rolling development branch) you will be presented with a message similar to the following:
 +<code>
 +You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
 +but Slackware version 15.0+ appears to be installed.
 +Slackware -current is the development (i.e. unstable) tree.
 +Is this really what you want?
 +</code>
 +
 +This is to be expected and you can proceed. The '+' in the Slackware version number means it's the development cycle //after// 15.0 (in this example) was released.
 +
 +</note>
  
 ==== Blacklisting ==== ==== Blacklisting ====
Line 30: Line 53:
  
 ===== Usage ===== ===== Usage =====
 +Read this entire page before using slackpkg, especially the part about Full System Upgrades, if you are or plan to run Slackware -current.
  
 Slackpkg uses patterns to search install and remove packages. The pattern will be searched on the list of packages and any package that matches the pattern is shown. Slackpkg uses patterns to search install and remove packages. The pattern will be searched on the list of packages and any package that matches the pattern is shown.
Line 111: Line 135:
  
 Running slackpkg with this argument will produce a clean printout if there are any available updates. Running slackpkg with this argument will produce a clean printout if there are any available updates.
 +
 +===== Regular updates =====
 +
 +After the initial configuration, the easiest way to keep your system up to date is to enter these commands:
 +
 +Cause slackpkg to update its knowledge of the configured Slackware release:
 +
 +<code>
 +slackpkg update
 +</code>
 +
 +Check the Change Log for the configured release:
 +<code>
 +slackpkg show-changelog
 +</code>
 +
 +Generally, unless you know what you're doing you should install new packages since some of the existing packages may now depend on them.
 +
 +<code>
 +slackpkg install-new</code>
 +
 +Upgrade to the latest packages:
 +<code>
 +slackpkg upgrade-all</code>
 +
 +Clean up:
 +<code>
 +slackpkg clean-system</code>
 +
 +<note tip>For Slackware ARM/AArch64, Kernel upgrades are handled automatically - there is no need to re-generate the Initial RAM Disk.
 +For x86/64 you may need to run the ''geninitrd'' command.</note>
 +
  
 ===== Full system upgrade ===== ===== Full system upgrade =====
Line 121: Line 177:
   slackpkg clean-system   slackpkg clean-system
      
-It is always recommended to read the latest ChangeLogs and ''UPGRADING.TXT'' (found on the HTTP/FTP mirrors for each version) before doing any major system upgrades. +It is always recommended to read the latest ChangeLogs and ''UPGRADING.TXT'' (found on the HTTP/FTP mirrors for each version) before doing any major system upgrades. \\ There's [[howtos:slackware_admin:systemupgrade|a separate article]] dedicated to doing a full system upgrade which you should definitely read first. 
 <note>Pay attention to changed configuration files. Update them either by merging your customizations from the older configuration files (Slackpkg can optionally step through every changed configuration file and allow you to resolve the changes) or manually editing the new files after allowing Slackpkg to overwrite the old configuration files. You decide which way works best for you.</note>  <note>Pay attention to changed configuration files. Update them either by merging your customizations from the older configuration files (Slackpkg can optionally step through every changed configuration file and allow you to resolve the changes) or manually editing the new files after allowing Slackpkg to overwrite the old configuration files. You decide which way works best for you.</note> 
 ===== External Links ===== ===== External Links =====
  
-  * SlackPKG home page: [[http://www.slackpkg.org/]] +  * SlackPKG home page: [[https://slackpkg.org/]]
-  * SlackPKG project on SourceForge: [[http://sourceforge.net/projects/slackpkg/]]+
  
 <!-- Please do not add anything below, except additional tags.--> <!-- Please do not add anything below, except additional tags.-->

Trace:

QR Code
QR Code slackware:slackpkg (generated for current page)