Subject: handling machine-dependent files in syspkg
To: None <>
From: Jeff Rizzo <>
List: current-users
Date: 05/18/2003 21:47:01
So, I just started playing around with syspkg the other day, and
it's got a lot of potential, but looks like it's suffered a little
bitrot since its initial commit over a year ago.  I noticed that
a few packages are referred to in the setlists that don't have
corresponding packages in the distrib/syspkg/sets directory.  So,
I figured this was a good way for me to help out, and I've started
creating packages for this missing stuff, which I'll send-pr

As I work on it, though, I've noticed a couple of areas where
there doesn't currently seem to be a good answer, unless I'm
missing something (which is likely the case).  One of them
is the handling of machine-dependent files or lists - the
current packages seem to have a largely i386 slant to them.  
Is it OK to just add MD files to non-machine-specific syspkgs?
For example, the i386-specific (and amd64, I guess)
 "./usr/mdec/pxeboot_ia32.bin" shows up in the PLIST for 
base-sysutil-bin, but the macppc-specific "./usr/mdec/ofwboot.elf"
does not, despite it being labelled as such in 
distrib/sets/lists/base/md.macppc .  I'd be happy to do some
work in this area, since I've currently got an interest in fine-grained
control of system installation, but I wanted to check with the list
first to see if anyone had any ideas or perhaps was already
working in this area...

Thanks, and sorry for the rambling email.  :)

Jeff Rizzo