This is the true magic in Slackware, every official package that you receive has a slackbuild file, in the source directory on the Slackware disk you will find the slackbuild files and source code for every package.This availability in the source directory allows you to view all options/modifications that were done to a package and if you need you can modify the script and arguments to fit your needs.In contrast the package building tools are somewhat similar to the package retrieval tools but rather than downloading a pre-build package they retrieve a build script (which can be customized and the subsequent source code allowing the user to custom compile an application for their system and their needs, once the application has been compiled the scripts pass the proper instructions to utilize the resulting binaries and build a Slackware formatted package that properly interacts with the Slackware package management tools.
When maintaining a server or even a personal system a certain amount of control must be given to the administrator, the control and simplicity of Slackware package management is what may in fact make you want to try Slackware.
In terms of security and accountability Slackware is excellent because it beings you software in the condition that the authors intended.
If you want to review the installed files for a package to find all files that were installed in the /bin directory, let say we are looking at the pkgtools package, you can run the command ‚Äúcat /var/log/package/pkgtools-13.0-noarch-3.txt|grep /bin/‚Äù.
In a similar fashion Slackware moves the text files from /var/log/packages to /var/log/removed-packages when you remove a package from your system, this makes it easier to have adequate tracking of what you have installed and what you removed and when each action was taken, this will help you greatly if you are wanting to replicate the list of installed packages from one server to another, you can easily write a script to compare the output of the folders on both systems and output a resulting file of non-matching packages that you can later use in a script for automatic installation..
Many users decide to use Linux based operating systems because of the freedoms they enjoy, included in the list is the freedom to choose the right tool for the job.
The Slackware package management schema is a model for displaying the choices that are available to the users.
Now because of the quality of various tools you have options for various functionality when it comes to package management and installations.
The main three methods of installation are listed below: To install Slackware from a pre-built package you can use installpkg, upgradepkg, swaret or slapt get.
Included in the slackbuild archive are the build script, license information, .desktop files (if needed), icons, and a file that tell you the version, source download location, md5sum, supported architectures and the author of the script.
There is also a mailing list and an irc channel available if you have questions or experience problems.
The official and many of the third-party package management tools in Slackware try to keep away from automatic dependency resolution so that the administrator is in full control of the system.