Visit Jeremy's Blog.
Go Back > Blogs > jheengut
User Name


Rate this Entry

Automatise additional Installation of software in Slackware

Posted 11-09-2015 at 11:11 AM by jheengut
Updated 11-09-2015 at 11:16 AM by jheengut

Slackware being an Advanced Operating System, is the oldest living Free/Libre Open Source Software Distribution in the world. Major tasks are still performed using the text driven ncurses as a Graphical User Interface and expects the Power User to configure the system aka /etc configuration files by hand. A DVD installation covers everything from a file,web,ftp,mail,.. Server to a complete Desktop and in addition to the TeX typesetting system. There is virtually no limit from which media the system can be installed from a pen drive, to optical media, to TFTP and even from the internet.

In the case of additional software needed, in the past the best way to do so was download the source code, compile and install the hard way. This setup has the liability that the particular software is non-upgradeable since the package manager is unaware of the software. In this respect, slackbuilds has been developed with a view to create software packages in a standard manner which can be shared and upgraded. There are many Slackware contributors who create additional software which be downloaded and installed manually using installpkg. Some even base their packages with slackbuilds so there is no need to compile manually.

There are two tools which automatise these processes.
The first tool sbopkg which download slackbuilds files from and is used to automatically download, compile and install software, in fact several software can be installed using SBo queues.
The second tool is actually a plugin to the slackpkg software manager. Slackpkg is a software manger which can be used to download patches, ie, software updates, to keep the system up to date, install new software and even upgrade to a new version. The only caveat being a singular repository is allowed. But slackpkg+ removes this limitation to allow multiple repository access, even a local directory can be used. It also can be configured to enable multilib, in slackware parlance, the capability to run 32bit software under a 64bit Slackware machine.

After a standard install,, enable a repository in slackpkg.

emacs /etc/slackpkg/mirrors
uncomment a slackware mirror.

Then update the keys.

slackpkg update gpg
Update the latest package lists

slackpkg update
remove superfluous software packages

slackpkg clean-system
Upgrade all packages

slackpkg upgrade-all
Install new software in case the OS was upgraded.

slackpkg install-new
Both the sbopkg and slackpkg+ tools have to be downloaded and installed manually.

From and

Install using installpkg

installpkg sbopkg-0.37.1-noarch-1_wsr.tgz slackpkg+-1.5.0-noarch-1mt.txz
Update sbopkg and slackpkg

slackpkg update gpg
slackpkg update
slackpkg upgrade-all
slackpkg install-new

sbopkg -r
sbopkg saves software packages in /tmp. They can be saved to a local repository and shared under an http or ftp server for local LAN access.
To be updated :: ssh access is currently unavailable.

More info available here alien slackpkg+.
and automatise additional installation
Posted in Slackware, Linux, Unix
Views 2119 Comments 0
« Prev     Main     Next »
Total Comments 0




All times are GMT -5. The time now is 04:35 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration