mkpkg 
Copyright 2005 - A.J. Venter

Licensed under the GNU GPL

OVERVIEW:
This is a small toolkit for automagically building slackware packages
it was basically created by reading the instructions in "The perfect package"

It should work on most packages, however it won't work unless the source package contains
a makefile. Write one if you have to (it's not hard), a simple one will suffice
if it handles "install" it's fine. If the Makefile handles "DESTDIR" it will use 
this to make the package (e.g. not actually installing the sources, you need 
to install the package afterwards), if not, it will use installwatch (so you need 
that - it comes with checkinstall). 
In the latter case there is no option but to do a real install, but the package
means you can uninstall if needed. 
As of version 0.0.19 mkpkg has the ability to attempt to automatically handle
dependancies. Unlike swaret it can also handle most dependancies for other
programs (not just libraries), it then writes these into a slack-required file
for you. This whole process however is more of an art than a science, so
it requires you to manually review the slack-required file in your editor.
Having the slack-require file should allow slapt-get like systems to 
handle the dependancies of your package automatically.

mkpkg is made up of one simple shell script (called mkpkg.sh) and a couple of 
supporting binaries. When you are asked to type the description, don't worry
about formatting, just type it (but do follow the norm of putting an empty line
after the first line) - mkpkg will format your slack-desc file for you.

mkpkg logs your configure options, that way, if you build later (or build an update)
you get a reminder of the options you used before !

You will find your package in /usr/share/mkpkg
And the tree to rebuild it (using makepkg) in /usr/share/mkpkg/PACKAGE_NAME

USAGE:
Extract the source package:
change into the extraction directory
be root
run mkpkg.sh

CONVENIENCE:
If only you build packages on the current system, you can create
/usr/share/mkpkg/builder.profile with these lines:

#Your full name
BUILDER_NAME="Enter Your Name Here"
#Your email address
BUILDER_EMAIL="myemail@mydomain.tld"
#Your initials
PACKAGE_INITIALS="EYNH"
#Your preffered text editor
EDITOR="mcedit"

If you don't specify an editor in builder.profile mkpkg will try to use
vim

Edit the values, and mkpkg will no longer ask these questions

This package was actually created with mkpkg !

SHORTCOMINGS:
It's very hard to tell version numbers of packages that are badly named
(e.g. not having a dash after package name) whats worse is that it
gets even harder when package name contains a dash, ergo OpenLab
replaces all dashes in package names with underscores. Not following
this can break things.

MKPKG is the default package builder for the OpenLab distribution (a slackware
derivative)
