Slackware Package Management

 

Package structure. Slapt-get or Slackpkg?

What is the difference between them?
Slackware is the most frequently criticized aspect of other GNU / Linux users; The scarcity of official packages is that they do not contain information about their dependencies and do not have an advanced official package manager that controls dependencies. Although the lack of control of dependencies seems to be a weakness for some users; in fact it is not. Thus, there are no dependency problems arising from the package management system while checking dependencies. This is an important point for a stable system. Slackware package management is left to the user as system administrator with officially provided package management tools (pkgtool, installpkg, removepkg, upgradepkg). The system administrator must determine the required program and the dependencies of this program and compile it in the correct order, or install the binary packages for the precompiled system together with their dependencies. The Slackware package management system is based on simple * .tgz and * .txz packages that do not contain any information about their dependencies. These packages are binary packages ready to be installed on the system with the package management tools officially provided by Slackware. In Slackware, the system administrator has full control over the system; parallel to this, it is essential that Slackware does not prefer an advanced package manager, which checks the dependencies of a package and adds the dependencies to the system via a central server. however, there are still informal and unofficial projects developed to provide advanced Slackware package management. An example of this is the “Slackware APT (command line: slapt-get, graphical: gslapt)” project developed on the basis of Debian's APT package management system and distributed under the GNU General Public License (GPL).
With Slackpkg, SlackBuild, SBo and Sbopkg, the Slackware philosophy allows easy system administrator-centric package management and update.
SLACKPKG
With the ana slackpkg ”tool located under the Slackware main directory tree and included with the installation, the software included in the distribution; in other words, it is possible to update your operating system. First, open the file / etc / slackpkg / mirrors in a text editor as an administrator, go to the line containing your own version of Slackware and the most suitable mirror for you to update, delete the “# ındaki at the beginning of the line, and save the file on it. Then as an administrator;
# slackpkg update
# slackpkg upgrade-all
# slackpkg install-new
your system will be updated. You can use these three commands for your future updates, the first update process will be executed from the mirror you selected in the first update process.

SLACKBUILD
If you want to install a package on your Slackware machine that is not included in the official version, you must create the dependency list for that package and your version of Slackware yourself. You will then need to follow the dependency sequence and compile each program and library from the source code and install it on the system. When packages are compiled from source code and installed directly on the system, then updating or removing packages from the system requires much more effort than the official binary packages; therefore, installing software directly from the source code is not a useful way. This problem can be overcome by using lack SlackBuild ”scripts, as Patrick Volkerding used to compile official Slackware packages. When a SlackBuild script is run, the compilation is performed automatically by following the commands inside the script and the Slackware binary package is generated from the source code. The resulting Slackware binary package can be easily installed on the system with package management tools, and then upgraded and removed. If you wish, you can rearrange the SlackBuild script to optimize the binary package you will build according to your processor architecture.
SBo (SlackBuilds.org)
For many non-official software SlackBuild scripts can be found in the SBo repository (http://slackbuilds.org/repository/). SlackBuild scripts in the SBo repository are highly reliable because they are tested by advanced users and some Slackware developers before they are included in the repository. With a SlackBuild script, any software is simply converted into a binary package from the source code as follows: Save the source code and the compressed archive files containing the SlackBuild script to your computer, extract the compressed archive file containing the SlackBuild script into a directory, and extract the compressed source code archive into a directory. Move the SlackBuild script to the directory where you saved it, and run the SlackBuild script as an administrator. As a result of the automated compilation process through the script, if all dependencies of the software to be compiled are provided, the binary package with the extension TGZ will be created and registered in / tmp directory.
SBOPKG
If SlackBuild scripts and source codes for the program and dependencies you want to compile from the SBo repository are saved on your computer, unpacked the scripts and assembled in the same directory as the source code, then Sbopkg is a perfect tool for you to run each SlackBuild script. . Sbopkg is an unofficial, command-line and dialogue-based, unofficial Slackware tool that provides synchronization with the SlackBuilds.org repository, capable of searching for SBo packages from the repository, as well as advanced package managers, and capable of compiling and installing packages via SBo SlackBuild scripts from source code. . Sbopkg uses the Slackware pkgtool tool to install the desired packages from the SBo repository. The Sbopkg tool does not have a check mechanism for dependencies on Slackware packages. Information about the dependencies of a package is available in the “README” file in the compressed archive file containing the SlackBuild script of that package; but this information is not used by Sbopkg when building a package. If you want to install a package with the Sbopkg tool, the package, the dependencies and subdependencies of the package must be correctly placed in the Sbopkg build list in the order of dependency and then the package build process should be executed. You can obtain the Sbopkg tool and related help documents from “http://sbopkg.org”.
Resources:
http://slackware.org/
http://slackbook.org/
http://slackpkg.org/
http://slackbuilds.org/
http://sbopkg.org/
http://software.jaos.org/