For those users, the traditional solution has been to download the source code for desired applications and compile them manually.
This works, but introduces another set of problems associated with managing those applications; version updates and such require more of the admin's time than precompiled packages, and lack of notes will often mean that the admin forgot which configure flags were used earlier (as well as any other special issues encountered).
What makes slpkg to distinguish it from other tools; The user friendliness is its primary target as well as easy to understand and use, also use color to highlight packages and display warning messages, etc.
code-block:: bash Required root privileges $ tar xvf slpkg-3.2.7gz $ cd slpkg-3.2.7 $ ./If you want to build slpkg for use with Python 3.x (needs the optional dependency python3) pass the script PYTHON3=yes, like: PYTHON3=yes ./Installed as Slackware package Uninstall: $ slpkg -r slpkg or $ removepkg slpkg Using pip:..
code-block:: bash $ pip install slpkg --upgrade Uninstall: $ pip uninstall slpkg Data remove run from source code: $ python Binary packages: Slackware: `slpkg-3.2.7-i586-1_`_Upgrade-------From version '2.1.4' you can update slpkg itself with '# slpkg update slpkg'.
The Slack project is maintained by a small group of people, but we want the scripts in our repository to be representative of the entire Slackware user community.
There's no way that the few of us can possibly write scripts for all of the extra applications that users want to have, so we depend on YOU to help us out.
Here is some maps that you want You need to know just 3 things: what version of spring do you want, what version of Slackware is running, and what kind of architecture you have.
To know what version of spring, you just need to go to check the last version.
Slpkg works in accordance with the standards of the organization to builds packages.
Also uses the Slackware Linux instructions for installation,upgrading or removing packages.
In our opinion, the best solution to this problem is for the admin to automate the compile process using a Slack Build script.