A package management utility for use with the Cross Linux From Scratch systems. PackManUtil is an online application control implemented by Shell (bash) scripts originally designed for use with an x86_64 multilib Cross Linux From Scratch (LFS) based system to simplify the process of construction of additional packages. The seed was planted for PackManUtil because I wanted a way to easily create a list of installed programs, libraries and directories to the Wiki CBLF. Thus, the function 'Tamarin' is the original PackManUtil.From its humble beginnings PackManUtil went to a construction system for Community Beyond Linux From Scratch (CBLF). I have a small cluster of heterogeneous machines at home using any CLFS. Although the number of machines is not large, once you've manually built the same package multiple times, it loses its luster. The next step in life PackManUtil was support for building, installing and removing packages. Finally PackManUtil supported the use of Paco and support has allowed for the installation of the source or using pacoballs.PackManUtil is written, tested and used daily on x86_64 multilib 32-bit PowerPC and i586 CLFS systems. Both 1.0.0 and 1.1.0 release have been used PackManUtil. It has never been tested on a Linux From Scratch (LFS) system, but there is a strong probability that it will work without issue.PackManUtil has been tested on Slamd64, version 12.0 system. The 64-bit builds worked with some exceptions. Many 32-bit builds also work, but the toolchain on Slamd64 is different from the LFS and not all 32-bit builds worked. PackManUtil has also been tested on a very minimal version i686 Slackware 12.0 install. No problems were encountered on the Slackware system. However, PackManUtil is intended to be used on a CLFS x86_64, ix86, or 32-bit PPC and there is no official support for Slamd64 or Slackware.Some test was done using scripts provided by SlackBuild SlackBuilds.org or Alien BOB. Testing to date has shown that if the extension '. SlackBuild is removed, these scripts will work with PackManUtil as well, but the source archive must be found independently. In addition, the archive bit set for use with Slackware or Slamd64, ie packets Slack (those with extensions. Tgz) May also be installed using PackManUtil they are stored in the correct directory. Once again, there is no official support for these more methods.In paco support for monitoring installation file, PackManUtil also supports the use of Installwatch and Slackware pkgtools.If using PackManUtil, we would appreciate a e-mail quick to let us know what you think. Even if you think PackManUtil stinks and it's a waste of our time working on.