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.
The GUIShell project is a collection of utilities facilitating the use of the GTK+ toolkit in shell scripts through the gtkshell utility. The ACE configuration environment provides sample scripts utilizing gtkshell for desktop utilities. rootcat provides the ability to display messages to the root window using Xft, allowing one to write status display scripts.
LMDBG is a collection of small tools for collecting and analyzing the logs of malloc/realloc/memalign/free function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks and double frees. However, unlike others, LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze an application on a per-module basis.
make project is a command line program which makes project skeletons. It automates the task of starting a new project with the information provided from the commandline. The package created by default is a "hello world" project of the selected skeleton which is managed with autotools. There are skeletons for bash, C, C library, Python, C++, C++ library, and Perl.
gc-utils is a small set of scripts that let you import and update CVS repositories into git very easy and let you export patches back into a CVS working copy. To makes the exchange easy, gc-utils stores the CVS working copy into a subdirectory and receives all information from there whenever necessary.
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.