Introduction to PackManUtil
PackManUtil is a command line application implemented through shell (BASH) scripts originally created for use with an x86_64 multilib Cross Linux from Scratch (CLFS) base system to simplify the build process for additional packages. The seed for PackManUtil was planted because I wanted a way to easily create the list of installed programs, libraries, and directories for the CBLFS Wiki. Thus, the function 'wikicontent' is the original PackManUtil.
From that humble beginning PackManUtil grew to be a build system for Community Beyond Linux from Scratch (CBLFS). I have a small cluster of heterogenous machines at home all using CLFS. Although the number of machines is not large, once you've manually built the same package a few times it looses some of its luster. The next step in PackManUtil's life was providing support for building, installing, and removing packages. Eventually PackManUtil supported the use of paco and this allowed support for installing from source or using pacoballs.
The x86_64 architecture is a multilib architecture and the standards recognize that. Being an engineer and having worked in the nuclear and aerospace/defense industries, I'm a stickler for standards. Although "pure 64-bit" is standards-compliant, these distributions require the use of wrappers that aren't needed in multilib distributions to accomplish things such as Flashplayer support in Firefox. Additionally, they often aren't standards-compliant and use /lib, /usr/lib, etc. for 64-bit libraries. So, I'm always on the look out for multilib x86_64 Linux distributions. When Slamd64 released version 12.0, Slamd64 provided multilib support. As a multilib distro, I was curious to what extent PackManUtil would work "as is" and how much effort would be required to fully support Slamd64. Thus was added support for Slamd64 to PackManUtil.
PackManUtil has been tested and used daily on x86_64 multilib and i586 CLFS systems. Both are built using the "Bender" release. It has never been tested on a Linux from Scratch (LFS) system, but there is a high probability that it will work without issue.
PackManUtil has been tested on a Slamd64, version 12.0 system. The 64-bit builds work with a few exceptions. Many of the 32-bit builds also work, but the toolchain on Slamd64 is different than on CLFS and not all 32-bit builds work yet. PackManUtil has also been tested very minimally on an i686 Slackware, version 12.0 install. No problems have been encountered on the Slackware system.
In addition to supporting paco for tracking file installation, PackManUtil also supports the use of Installwatch and Slackware's pkgtools. Some testing has been done using SlackBuild scripts provided by SlackBuilds.org or Alien BOB. Testing to date has found that if the '.SlackBuild' extension is removed, these scripts will work with PackManUtil as well, but the source tarball needs to be retrieved independently. In addition, binary archives created for use with Slackware or Slamd64, i.e. Slack packages (those with .tgz extensions) may also be installed using PackManUtil if they are stored in the correct directory.
Required Dependencies
One or both of the following clients is required to retrieve files:
Recommended Dependencies
Cross Linux from Scratch
I use a Cross Linux from Scratch (CLFS) version 1.0.0 multilib system as my everyday operating system. After building my first CLFS system, I became involved in Community Beyond Linux from Scratch (CBLFS) and began to add build instructions at the CBLFS wiki. Apparently I added enough instructions that I received the honor of becoming an editor of CBLFS.
I still add and edit build instructions at the CBLFS wiki but I am essentially finished installing all the packages I use on my machine. PackManUtil evolved from my needs on my machine. I can be found from time to time at the #cross-lfs channel on freenode.net if you have any compliments or questions about PackManUtil. Complaints and problems should be addressed to /dev/null. :)
Check out CLFS if you are looking for a technical challenge. Please note that the Cross Linux from Scratch Logo is not an official logo of the Cross Linux from Scratch Project. You are, however, welcome to use the image as long as you provide a notice that it is not an official CLFS logo.
