From: lew.pitcher@digitalfreehold.ca   
      
   Today, I installed four (self-built) packages on my Slackware 14.2 system   
   in order to play "MineTest". Admittedly, this was a minimal install; with   
   just those packages that MineTest absolutely required in order to   
   function.   
      
   In retrospect, while the three "support" packages each provide facilities   
   that will be useful elsewhere on my system, I don't actually have a use   
   for them other than to get MineTest working. So, the installation, for me,   
   is "all or nothing": all four packages, or none.   
      
   I thought to myself that it would be nice to have a way to provide a   
   Slackware "meta" package; a package that, through it's installation,   
   installs a number of /other/ packages. I could have a "MineTest" meta   
   package that, when installed via installpkg, would have installed the   
   four independent packages that make up my MineTest installation.   
      
   What I came up with was a simple package that consists of   
    a tmp/ subtree containing the actual packages to install, and   
    an install/ subtree with a doinst.sh that simply invokes installpkg(8)   
    on each of the packages supplied in the tmp/ subtree. This doinst.sh   
    would then uninstall(8) the package that contains it.   
   And, voila, a poor-man's Slackware meta package.   
      
   Of course, this is very rough, has no provisions for upgradepkg(8) nor a   
   removepkg(8), and is likely very fragile. But, for my experiment, it   
   worked.   
      
   So, I ask, has anyone here experimented with this metapackage idea? If   
   so, how did you approach it, what did you do, and how did it turn out?   
   --   
   Lew Pitcher   
   "In Skills, We Trust"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)