Re: Base packaging

P.S.  How do you handle the packlist generation?  The ports system
doesn't automatically generate these things, as far as I can tell, and
I didn't see anything that you've added to do this.

My agenda, if you will, on this is to deal with:

   upgrades: portupgrade can grok packages.  If you had a good way to
   generate the package list, then we could make it a lot easier to do
   binary upgrades.  Thie would let me have a big meta-port that
   covers all the 'standard' things on the machine, including the os.
   Chances are good that some care would need to be taken in
   portupgrade to make sure that it doesn't use binaries in place that
   will be replaced.

   subsetting: with the proper set of subsetting, one could easily
   create packages such that they could install just what they
   needed.  It might be good to have a few like "minimal to boot with
   rc.d" and the like.

   nopriv: it should be possible to build a release w/o any privs at
   all.  NetBSD does this with hacks to install and pax to journal
   installation stuff in a certain mode and a new mkfs program to take
   that info and create a file system image that can be used in the
   target environment.

Warner