[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

Next revision		Previous revision
slackware:package_management [2012/12/30 05:54 (UTC)] – created, completed and copied from user test space mfillpotslackware:package_management [2018/03/03 20:03 (UTC)] (current) – [Brief Explanation of Slackware Packages] tlz means tar.lz since 'Wed Feb 14 19:48:51 UTC 2018' - compressed using lzip alienbob
Line 10: Line 10:
 is what may in fact make you want to try or continue to use Slackware. is what may in fact make you want to try or continue to use Slackware.
  
-====== Brief Explanation of Slackware Packages ======+===== Brief Explanation of Slackware Packages =====
  
 In terms of security and accountability Slackware is excellent because it In terms of security and accountability Slackware is excellent because it
-beings you software in the condition that the authors intended. What this+brings you software in the condition that the authors intended. What this
 means is that the Slackware community does not modify the source or add and means is that the Slackware community does not modify the source or add and
 remove functions from software beyond the author's design, unless a small remove functions from software beyond the author's design, unless a small
Line 29: Line 29:
 result in exploits that only effect the specific distribution which can result in exploits that only effect the specific distribution which can
 remain unseen remain unseen
-for some time because the original authors (those who know the applicationss best)+for some time because the original authors (those who know the applications best)
 were not responsible for the changes or aware of the changes. This additional were not responsible for the changes or aware of the changes. This additional
 liability is something that an administrator does not want hanging over their liability is something that an administrator does not want hanging over their
Line 39: Line 39:
 Slackware packages can be found with any of the following extensions: Slackware packages can be found with any of the following extensions:
   * tbz - Slackware package archive compressed using bzip2   * tbz - Slackware package archive compressed using bzip2
-  * tlz - Slackware package archive compressed using lzma+  * tlz - Slackware package archive compressed using lzip
   * tgz - Slackware package archive compressed using gzip   * tgz - Slackware package archive compressed using gzip
   * txz - Slackware package archive compressed using xz   * txz - Slackware package archive compressed using xz
Line 57: Line 57:
 abundant. abundant.
  
-====== Dependency Tracking ======+===== Dependency Tracking =====
  
 One of the major complaints by new users is the fact that Slackware does not One of the major complaints by new users is the fact that Slackware does not
Line 67: Line 67:
 functionality without introducing unneeded components. functionality without introducing unneeded components.
  
-===== Why restrict Automatic Dependency Resolution? =====+==== Why restrict Automatic Dependency Resolution? ====
  
   * Lack of administrative control   * Lack of administrative control
Line 78: Line 78:
 administrator is in full control of the system. administrator is in full control of the system.
  
-====== Installation and Package Management Tools ======+===== Installation and Package Management Tools =====
  
 There are many package management tools for Slackware,both official and from There are many package management tools for Slackware,both official and from
 third-parties, both groups are discussed below. third-parties, both groups are discussed below.
  
-===== Official Tools =====+==== Official Tools ====
  
 Included in the base installation of Slackware are two packages **pkgtools** and Included in the base installation of Slackware are two packages **pkgtools** and
Line 94: Line 94:
 you to use with the official Slackware servers. you to use with the official Slackware servers.
  
-==== pkgtools ====+=== pkgtools ===
  
 pkgtools contains the following executable applications pkgtools contains the following executable applications
Line 111: Line 111:
   * **makepkg** - This application is used to create a new Slackware package from the contents of your current directory.   * **makepkg** - This application is used to create a new Slackware package from the contents of your current directory.
  
-==== slackpkg ====+=== slackpkg ===
  
 slackpkg is to be used to install official slackware packages from the slackpkg is to be used to install official slackware packages from the
Line 125: Line 125:
 </note> </note>
  
-===== Unofficial Tools =====+==== Unofficial Tools ====
  
 The unofficial tools are tools that were made by third parties which are not The unofficial tools are tools that were made by third parties which are not
Line 151: Line 151:
   * **swaret** - This tool is designed to replicate the functionality of the Debian apt-get system, you identify the repositories you would like to use and it allows you to download and install packages from the specified location, this tool also attempts dependency resolution.   * **swaret** - This tool is designed to replicate the functionality of the Debian apt-get system, you identify the repositories you would like to use and it allows you to download and install packages from the specified location, this tool also attempts dependency resolution.
   * **slapt-get** - This tool is designed to replicate the functionality of the Debian apt-get system, you identify the repositories you would like to use and it allows you to download and install packages from the specified location(s).   * **slapt-get** - This tool is designed to replicate the functionality of the Debian apt-get system, you identify the repositories you would like to use and it allows you to download and install packages from the specified location(s).
-  * **[[howtos:slackware_admin:building_packages_with_sbopkg|sbopkg]]** - This tool syncs with the slackbuilds.org build script repository, it is used to pull build scripts, upon choosing the scripts to build it allows you to choose the build order and also customize the scripts. Upon completion of the scripts it will allow you to build a Slackware package or to build and install the package. //If you choose to use a third party tool, this is the one I recommend; it has the highest probability or package stability and allows you to customize your packages.//+  * **[[howtos:slackware_admin:building_packages_with_sbopkg|sbopkg]]** - This tool syncs with the slackbuilds.org build script repository, it is used to pull build scripts, upon choosing the scripts to build it allows you to choose the build order and also customize the scripts. Upon completion of the scripts it will allow you to build a Slackware package or to build and install the package. 
 +  * **[[https://github.com/dslackw/slpkg|slpkg]]** is a powerful software package manager that installs, updates, and removes packages on Slackware based systems. It automatically computes dependencies and figures out what things should occur to install packages.
  
-====== Installation Methods ======+===== Installation Methods =====
 With of the quality of various tools, you have options for various With of the quality of various tools, you have options for various
 functionality when it comes to package management and installations. The main functionality when it comes to package management and installations. The main
Line 161: Line 162:
   * Build a custom package from a build/slackbuild script   * Build a custom package from a build/slackbuild script
  
-===== Install from a Pre-built Package =====+==== Install from a Pre-built Package ====
  
 To install Slackware from a pre-built package you can use **installpkg**, To install Slackware from a pre-built package you can use **installpkg**,
Line 176: Line 177:
 </code> </code>
  
-===== Compile the Application from the Source Code =====+==== Compile the Application from the Source Code ====
  
 Many people have grown accustomed to this method over time, but it is not Many people have grown accustomed to this method over time, but it is not
Line 184: Line 185:
 will save you time and effort in the future. will save you time and effort in the future.
  
-=====Build a Custom Package from a Build/slackbuild Script =====+==== Build a Custom Package from a Build/slackbuild Script ====
  
 This is the true magic in Slackware, every official package that you receive This is the true magic in Slackware, every official package that you receive
Line 207: Line 208:
 package from a slackbuild, and how to build custom scripts. package from a slackbuild, and how to build custom scripts.
  
-====== Package Tracking ======+===== Package Tracking =====
  
 When using Slackware, you have the ability to track the installation date, When using Slackware, you have the ability to track the installation date,
Line 269: Line 270:
 will not show up in the Table of Contents --> will not show up in the Table of Contents -->
 {{tag>slackware package_management author_mfillpot}} {{tag>slackware package_management author_mfillpot}}
- 

Trace:

slackware:package_management ()