Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



Alien’s SlackBuild Toolkit

Some time ago I posted a blurb about “AST”, which is my “Alien’s SlackBuild Toolkit”. It is a web-based application for people who want to build a package for Slackware and don’t feel comfortable writing a build script. AST will ask you a few questions and then produces a SlackBuild script and slack-desc file which will usually need only small final adjustments.

The SlackBuild script it produced was derived on the template I use for my own scripts (see Since my previous blog post, I have received feedback from users who wanted to have more choice in the template to use for their scripts.

So, I sat down at the drawing board and expanded AST. The result is that you can now choose from three templates. The default template is still my own, called “web“. The two others are “sbo” which is based on the template script, and “bare” which is modeled after the scripts being used in Slackware.

I hope you like it – feedback always welcome.

Have fun! Eric


Comment from schultzter
Posted: September 25, 2009 at 15:55

Wow, that’s cool! I was getting started learning to write slackbuild scripts and this sure smooths the learning curve.

A couple things I noticed though:
– A field for the MD5SUM for the source files would be nice since they are often provided and known upfront;
– i486 and x86-64 are not mutually exclusive so I would re-arrange that whole bit to allow both or either
– the info file seems to missing information that is provided (i.e.: maintainer)

Thanks again!

PS.: I’ve found one example (on where uname -m is used to determine ARCH but why isn’t it used by default?!

Comment from specialized
Posted: September 25, 2009 at 23:37

Great Man!!! you’re a god of the slackware heaven, i wish, in a moment of my life, to know all the thing that you know, but im just a little slacky nerd right now, thanx for AST !!!

Comment from dgt
Posted: November 24, 2009 at 17:26

Hello Sir, I am still trying to get Package Creation down for Slackware but am unsure of where to start for backgroud knowledge. I have a good handle on K&R C but is any additional Programming experience required to use AST properly?

Comment from alienbob
Posted: November 25, 2009 at 09:55


If you want to know more about writing SlackBuild scripts, then you could read this article on SlackWiki: for some more background.

The AST web-application really requires no programming knowledge at all. You only have to fill out a few fields in the form, and AST generates the shell script code that you copy/paste into a file on your local Slackware machine.

It really helps if you have a knowledge of (bash) shell scripting, but in many cases the SlackBuild script code generated by AST is generic enough that it will work with minor to no modifications.

You may encounter situations where the program sources which you want to compile into a Slackware package are so clumsily written (or contain bugs) that you have to have some knowledge of C and the ‘patch’ program in order to successfully build a binary. Luckily, such situations are not common.

Cheers, Eric

Pingback from How to build a Slackbuild script?
Posted: October 30, 2010 at 15:22

[…] You also have the Slackbuild toolkit from Eric H.:…build-toolkit/ […]

Write a comment