Loki Setup is a graphical installer for Unix applications. It features descriptions of the package to install in XML, a GTK interface that can be dynamically redefined by the user with Glade, raw and ncurses console interfaces, and the automatic generation of uninstall scripts. It has been successfully used on many Linux and UNIX platforms. It includes tools for uninstalling, patching, and recovering installations. It operates independently from any package managers.
rtldi is an ELF program interpreter that makes it possible for executables to use their own ld-linux.so.2 and libc.so.6 and associated shared libraries, independent of the default versions installed in /lib and any other executable. It facilitates the simultaneous interoperation of programs that were originally linked using different generations of glibc6. In theory it should not be necessary, but in practice glibc6 has not always been backward compatible.
Wine-doors is an application designed to make installing Windows software on Linux, Solaris, or other Unix systems easier. It is essentially a package management tool for Windows software on Unix systems. It is developed and styled to fit in with the GNOME desktop, but is fairly portable and a user interface could be developed for KDE. The main goals are to replace winetools, allow flexible application management, provide Queue processing capabilities, provide Application Database integration, avoid global native overrides, automatically add items to the desktop menus, and allow users to manage their Windows applications with profiles and bottles.
spill manages symbolic links under one tree which point to matching filenames in another. When individual projects are configured with project/version-specific -- prefix= settings, to keep their installations segregated, spill can make them appear to be installed in a common place, e.g. under /usr/local. It can also delete the links associated with a particular program. It is similar in concept to various other programs such as stow, depot, and relink. However, it's written in C, so it isn't reliant on an interpreter being available. It also doesn't assume complete control of the directory tree where the symbolic links are created. It can create both absolute or relative symbolic links, the latter being more convenient in some setups.