depfinder finds the dependencies of Slackware packages. The dependency list can be output to stdout, to a .dep text file without version information, or to a slack-required file with version information. depfinder is very fast; its speed is mainly due to the C++ code that is used in depfinder to find in which package each individual library is included. It also has support for running multiple jobs, which makes it a lot faster when used with multiple CPUs/cores. depfinder supports detecting dependencies of binary files compiled with languages such as C or C++ and it can also detect Python dependencies.
Cinabox (Continuous Integration in a Box) automates the setup of a Continuous Integration (CI) system by doing The Simplest Thing That Could Possibly Work. It consists of two simple scripts to set up a cruisecontrolrb CI server from scratch on an Ubuntu 8.04 system: one script to bootstrap Ruby, and another script to set up CI.
gccwrap 32bit is a set of simple wrapper scripts to make it easy to compile 32-bit only programs with uncooperative Makefiles on 64-bit systems. You can just use "32bit make" to compile them and the wrappers will transparently add any -m32 options needed and also do some other transparent fixups. This package requires a Linux distribution with proper FHS compliant -m32 / multilib support like SUSE, Fedora, or Mandriva.
Releaser is a set of scripts to automate and manage the tasks related to software package releases. It is designed to be modular and to make it easy to both select a particular set of actions associated with releases of a particular project (such as changelog generation, uploading of tarballs, posting announcements to mailing lists), and create new actions that integrate seamlessly into the process. Its status is still somewhat experimental, but the most basic functionality is there.
autogen.sh (a.k.a. buildconf) provides automatic build system preparation and is generally very useful to projects that use the GNU build system (i.e. the GNU autotools: autoconf, automake, and libtool). It is a POSIX shell script that is used for preparing a build system for compilation, verifying versions, ensuring necessary functionality, and overcoming many common build preparation issues.
pkgmake automates some steps when making software releases. It creates a copy of the development tree, optionally cleans it up a bit (i.e. removes CVS/* and .svn/*), tars it, places the tarball in the SOURCES/ directory, creates the corresponding .spec file from a provided template (and the data specified in the configuration/on the command line), and runs rpmbuild and/or debbuild as well as spec2arch. As a result, you will have packages for Debian and RPM based distributions as well as the PKGBUILD file for ArchLinux. Using relman as the recommended frontend to pkgmake, new software releases are as easy as calling relman with two parameters: the project name plus the release version - and all packages are made and distributed.