MIT/X Consortium License    
4.8/5 11
A package management utility for use with Cross Linux from Scratch systems.






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 'wikifi' 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.

PackManUtil is written, tested, and used daily on x86_64 multilib, 32-bit PowerPC CLFS and i586 systems. Both the 1.0.0 and 1.1.0 release have been used with PackManUtil. 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 worked with a few exceptions. Many of the 32-bit builds also worked, but the toolchain on Slamd64 is different than on LFS and not all 32-bit builds worked. PackManUtil has also been tested very minimally on an i686 Slackware, version 12.0 install. No problems were encountered on the Slackware system. However, PackManUtil is intended for use on a CLFS x86_64, ix86, or 32-bit PPC system and there is no official support for Slamd64 or Slackware.

Some testing has been done using SlackBuild scripts provided by 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. Once again, there is no official support for these methods.

In addition to supporting paco for tracking file installation, PackManUtil also supports the use of Installwatch and Slackware's pkgtools.

If you use PackManUtil, we'd appreciate a quick e-mail letting us know what you think. Even if you think PackManUtil stinks and is a waste of our time working on.
Last updated on August 10th, 2009
PackManUtil - Selecting the Package Version to BuildPackManUtil - Displaying the Build OptionsPackManUtil - Displaying the Build OptionsPackManUtil - screenshot #4PackManUtil - screenshot #5

0 User reviews so far.