Slackware GNU/Linux Packages by SukkoPera

On this site you will find a collection of software packages built for the Slackware GNU/Linux operating system, the mother of all GNU/Linux distributions.

I have built all of this packages for my personal use, according to my own preference, but then I thought they could be useful to other people, so I decided to put them online, to make them available for the masses.

The packages are sync'ed every night at about 3:30 GMT+1 with my local repository, so things might go crazy around that time.

Please note that I don't want my packages to be the best and/or most used out there. Everything here is available on a it works for me, I hope it works for you too basis.

If you want to be informed about the added packages, you can use the RSS 2.0 feed. Please note that, as the site is updated once a day, it is useless to update the feed every 5 minutes or so.

Oh, and yes, this site is hosted on Ubuntu, the only other decent GNU/Linux distribution out there.

Building environment and criteria

I usually choose the compilation flags so that they best suit my own personal needs, so there are a couple of things you should be aware of:

First of all, please note that some packages are quite experimental, so use them at your own risk.
I usually provide packages for all the dependencies any other package requires. Sometimes, if I don't see any usefulness for a dependency outside of the program, I even pack the dependency with the program package itself.
I am a KDE user, so I usually disable GNOME integration, if it is optional. Of course, I enable all the KDE integration options.
For those few programs that require GNOME libraries, I use the GWARE pre-built packages, as I don't want to go crazy compiling all those damn GNOME dependencies.
For graphical applications, I usually follow the freedesktop.org specifications, adding an icon for programs that should show up in both the KDE K Menu and the GNOME foot menu.
I try to avoid to rebuild packages already included among the official ones. I only do it when I need to enable support for some feature, or when I need a newer version.
I usually build packages on Slackware-current, so if you are using an older version, you might encounter dependency problems. In this case, you can rebuild the packages on your machine, using the provided build scripts, as explained further on. Actually, some of the packaged were built quite a long time ago, so sometimes your distribution might even be "too new" ;).
I usually build for the i486 architecture, optimizing for i686, exactly like the official packages. If you need packages for a different architecture, just rebuild them on your machine, changing the compilation flags in the build script.

Building method

Every package available here includes some sort of build script. It is also available in the packages themselves, together with any other files needed at compilation time, in the /usr/doc/<package name>/slackbuild directory. The main build script should always be named <package name>.SlackBuild, and is commonly referred to as the slackbuild.

My way of creating packages has evolved through the years, so the scripts can be of a few different kinds. My older packages have a stand-alone slackbuild, that you just needs to be run. Recently, I have developed some helper functions, and included them in a library, which is therefore needed at build time. In this case, all you have to do is to download the BUILD subdirectory, replicating the same directory structure. In there, you will also find all that is needed to create a new package: just copy new.SlackBuild, renaming it properly, and fill the slack-desc template. Take a look at the available scripts to get to know the available functions.

Also note that my very first packages have names ending with sukko, while later I switched to suk.

All of my build scripts can be considered public domain.

Download

There are a few ways to get the packages:

You can manually download and install them. In this case, just click here.
If you use Swaret to manage your packages, then add the following line to /etc/swaret.conf:

REPOS_ROOT=Sukkology%http://slackware.sukkology.net/repository

This way you will be able to install the packages with swaret --install <package name>.
If, instead, you use slapt-get for your package management duties, add the following line to /etc/slapt-get/slapt-getrc:

SOURCE=http://slackware.sukkology.net/repository/

Then, just use slapt-get --install <package name>.

Contacts

For any info or suggestion, please drop me a line: slackware at sukkology full_stop net.