Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

This is an old revision of the document!


There are a few ways of installing studioware applications. We have both pre-built packages and slackbuild scripts that create packages from source.

To make the process a little simpler we have two applications to download and install them: studiopkg for packages, and sepkg for building from slackbuilds. They both support queue files, and will even download the queues from our server if needed.

1) Preparing Studiopkg and Sepkg

First you need to grab the latest versions and install them with installpkg:


# installpkg studiopkg-VERSION-noarch-TAG.txz
# installpkg sepkg-VERSION-noarch-TAG.txz

Next step is to check that they are both pointing at the right branch.

Edit /etc/studiopkg/studiopkg.conf and change SWVERSION to reflect your Slackware version - eg:


The ARCH is worked out automatically.

You can also set CHECKGPG=ON or OFF for your needs. We recommend ON.

Edit /etc/sepkg/sepkg.conf and change SWVERSION to also reflect your Slackware version.

Once that is done they need to fetch the latest file lists from our servers using the -u flag. Additionally studiopkg needs to import our gpg key:

studiopkg gpg
studiopkg -u
sepkg -u

You should now be able to build/install packages.

2) Installation

We have three main categories of applications: audio, video and photo. They are maintained by queue files. There is also a 'full' queue.

If you want a certain category - say audio, then you can use either studiopkg or sepkg to download and build/install all the audio applications with the -q flag:

studiopkg -q audio
sepkg -q audio

When using studiopkg it will check the package md5 and gpg. If these are wrong you may need to retry the download and/or delete the cache using the delete-cache option. It will prompt for retry download. If it keeps throwing up an error then please contact us with the details.

3) Done

That's it. Now start using your apps.

Going Further

Queue Operations

Queues are the best way to handle installation as they can be adjusted as needed and it saves trying to remember options etc.

It is possible to use queues locally via shell redirection, or remote queues downloaded from our server. Note that our premade queues are in sbopkg format and have the .sqf extension, but for local queues any filename can be used.

Queue Examples

Local queues:

studiopkg -i < kdenlive.sqf
sepkg -i < kdenlive.queue

This will download the appropriate files one at a time and build and/or install them.

Note that it is probably a good idea to set noclobber in your shell, or accidently using '>' instead of '<' will wipe the queue file. For bash use 'set noclobber' and for zsh use 'setopt noclobber'.

Remote queues:

studiopkg -q kdenlive
sepkg -q kdenlive
studiopkg -q video
studiopkg -q full
sepkg -q video

We have queues for whole sections of packages - full, video, audio, photo (You don't need to specify the extension as .sqf is assumed). This makes it much easier to set up a machine with a categories of packages in one shot. The queues are on both our ftp and in git, so they can be downloaded manually and adjusted if need be.

Build Options

sepkg queues can take build options:

In the queue specify options after the application name:

ardour WIIMOTE=yes

To find out which build options are avaliable it is necesary to read the README or the SlackBuild in our git repo for the specific application. COMING SOON: We will have a list of applications and their directory branches to make finding them easier.

Other Operations

studiopkg can clean our packages from the system with either:

studiopkg clean
studiopkg clean-system

A dialog window will popup asking which ones to clean. This is similar to the way slackpkg works except it will ONLY list packages with our 'se' tag, so no other extra packages will be listed.

A full list of operations and options can be found here:


Slackpkg and sbopkg

It is possible to download and build/install using slackpkg (with the slackpkg+ plugin) and sbopkg. You will notice that our own tools are similar in some ways, but there are differences. For example, sbopkg has many more features for setting options, building queues etc. One main difference though is in the way that our tools handle queues of categories.

We recommend using our tools for installing whole categories as they were designed with this in mind and simplify the process of getting a machine up and running.

Later, either slackpkg or sbopkg can be used to search, build or install applications. A howto on setting up slackpkg and sbopkg can be found here: http://docs.slackware.com/studioware:slackpkg_sbopkg

* Originally written by dive

In Other Languages
Translations of this page?:
QR Code
QR Code studioware:quick_start (generated for current page)