Processes for building Porteus packages.

From Slackbuild

Download the SlackBuild tarball (from slackbuilds.org, for example). It will contain a .SlackBuild script (which is basically a shell script that does the compiling for you) as well as whatever other files will be required by the package.
Uncompress the tarball to a temporary directory.
Use wget to download the source code archive referenced by the .info script (in the DOWNLOAD line).
If necessary, edit the variables in the .SlackBuild script to bring it up up to date.
Run the .SlackBuild script as the root user. This is important for the package creation process because it allows, among other things, file ownerships and permissions to be set properly.
If the .SlackBuild worked, a Slackware package file will be found in /tmp. Use `ls -ltr /tmp` to find it.
Convert the .tgz or .txz Slackware package into a Porteus module
- tgz2xzm /path/to/slackware.tgz /path/to/porteus.xzm
- txz2xzm /path/to/slackware.txz /path/to/porteus.xzm

Used for packages that do not have slackbuild files associated with them.

Move the .xzm file to your porteus/modules directory (in my VM the full path is /mnt/sda1/porteus/modules, but yours may vary).
Run the command `activate /path/to/porteus/modules/newmodules.xzm` as the root user. If it worked you will see a window pop up (if you're using the desktop) confirming activation.
Once activated, modules remain active across reboots (if Porteus is installed to read-write media).

Copy it off of your virtual machine or USB key.
Check it into your Git repository in the Byzantium/porteus/packagename directory along with the SlackBuild and source tarballs. If the directory does not exist, create and `git add` it.
Check everything in and do a `git push` to keep the central repository up to date.