SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
mkslack - a SlackBuild generator script
(C) David Woodfall 2010
This slackbuild generator uses templates stored in usr/share/mkslack/templates
and a config file /etc/mkslack/mkslack.conf which you must edit for name,
email, copyright etc.
The slackbuild templates are based on the ones at slackbuilds.org and
shouldn't be changed too much apart from the aforementioned. In particular
the lines for man and info pages and <documentation> should not be edited
as the script will look for those lines to be exactly the same, and if not
needed, delete them.
The PRGNAM, VERSION, ARCHIVE recognition is very loosely done. It can find
standard source archives which can be .tar.gz .tar.bz2 or .tgz. If you have
a source archive with a '-' in the version number then mkslack will be
borked. In this case you can still use mkslack to build the slackbuild,
but you must edit it by hand before running it.
The new template detection system has not been extensively tested so please
give feedback, bug reports on any that don't seem to work. Mail me at firstname.lastname@example.org with name of software, download link etc.
Idea for use:
The initial slackbuild and info file are built by this script, and when
a test build/install is done and working, the files should be tweaked by
hand. Especially don't forget to fill in the rest of the details in the
.info. One thing to point out is that mkslack will overwrite these files
if run again!
This is only a starter kit! You ARE expected to edit the created files
by hand afterwards to remove unnecesary parts!
mkslack [options] <archive>
-h --help Usage.
-r --run Run SlackBuild after creation. Got root?
-i --install Install the package after running.
-l --list Pipe archive contents to /usr/bin/most and exit.
-v --version Version of mkslack.
The documents list in top level of source tree can be adjusted by command:
DOCS="SomeFile" mkslack <archive>
This will add 'SomeFile' to the list. You can also edit the DOCS list in
this script. Any that it doesn't find will be removed from the list.
Build can be specified by:
BUILD=2 mkslack <archive>
Otherwise it defaults to 1.
ARCH can be specified by:
ARCH=xxx mkslack <archive>
It defaults to i486 the same as a regular SlackBuild.
I have actually wondered if anyone had put together a tool like this, as 90-95% of packages don't actually need unique Slackbuilds; a common template with changed variables for name, version, and arch is sufficient.
Up to this point I have always just done it by hand, but that is repetitive and rather tedious. I'll have to check this out on my build machine.