slacktools - crappy shell scripts to build slackware packages
Copyright (C) 2004-2007  Peter Willis <peterwwillis@yahoo.com>

  ABOUT

Just a few scripts and tools i've thrown together to make managing a
slackware box a little easier.

slackpack   - unpacks an archive, runs slackconfig && slackmake, then removes
              build directory
slackconfig - handle the ./configure process of a package build
slackmake   - handle the make process of a package build, and the packaging
slackpkg    - called by slackmake to package compiled source as root
backoutpkg  - re-creates packages based on /var/log/packages/NAME and
              /var/log/scripts/NAME

  INSTALL

Copy each script to /usr/local/bin and make them executable:

  cp slack* /usr/local/bin
  chmod 755 /usr/local/bin/slack*


  USAGE

Run slackpack with a source tarball as an argument

OR

1. Untar a package and change into its directory.
2. Run slackconfig, with optional environment variables or arguments to
   ./configure. The defaults are usually sane enough.
3. Run slackmake. It tries to guess if the package supports DESTDIR,
   and if it does and 'make DESTDIR=`pwd`/_install install' works as a
   normal user, it'll run it again as root and run slackpkg to make a
   slackware package.

Poof! A new slackware package should be waiting for you in the current
directory if everything worked OK.

Backoutpkg works in the opposite fashion. Say you build a wonderful package and
installed it on your machine, then accidentally deleted the built package and
you don't want to build it again. `backoutpkg FULL-PACKAGE-NAME` will re-create
the .tgz package for you in the current directory.

  NOTES

I am aware there is another project called 'slacktools' out there, but they
have released no files so I have decided to name my tools in a sane manner.