On Tue, May 13, 2003 at 03:36:27PM +1000, Luke Mewburn wrote:
> On Tue, May 13, 2003 at 01:32:54AM -0400, Sean Davis wrote:
>   | On Tue, May 13, 2003 at 03:29:18PM +1000, Luke Mewburn wrote:
>   | > On Mon, May 12, 2003 at 11:46:33PM -0400, Sean Davis wrote:
>   | >   | Does this fix the issue where postinstall complains if /var/db/obsolete
>   | >   | exists but is empty?:
>   | > 
>   | > Probably not.
>   | > 
>   | > The question is, how are you building so that you don't have a populated /var/db/obsolete?
>   | 
>   | I run a script I wrote that does build.sh to a destdir, pax's up rescue,
>   | libexec, lib, bin, sbin, and usr, and then install that via cd / && pax
>   | -zrvpe -f /path/to/userland.tgz. that way i can just install from that .tgz
>   | on other i386 machines here. I then run etcupdate. /var/db/obsolete was
>   | initially created by /etc/postinstall at the end of an etcupdate a while
>   | back, and this has been going on since then.
> 
> So add destdir/var/db/obsolete to your .tgz file lists.
> /var/db/obsolete is part of the base set.
> 
> For that matter, why don't you just build the sets (build.sh has a friendy "sets" target :)
> and install from those?

Because then I'd have to deal with flist inconsistencies, which seem to
happen on a very regular basis if the mailing lists are to be believed. This
way I get just the userland stuff I want, and in one tarball so on another of
my boxes I can just upgrade the kernel (also autobuilt via another script) then

cd / && ftp -o - ftp://this.machine/netbsd/<date>/userland.tgz | pax -zrvpe

I of course should etcupdate on the other machines, but I tend to do that
less frequently. It'd be nice if etcupdate supported a configuration file
that you can fill with paths to files you want it to leave alone, so it
could do its thing without requiring user intervention, but i digress.

-Sean

-- 
/~\ The ASCII
\ / Ribbon Campaign                   Sean Davis
 X  Against HTML                       aka dive
/ \ Email!