Re: hardcoded -C argument to ${INSTALL}

At 9:26 PM -0400 5/6/03, Garrett Wollman wrote:
><<On Tue, 6 May 2003, Garance A Drosihn <drosih_at_rpi.edu> said:
>
>>  I think this "remove stale pieces" issue is one that we have
>>  to find a decent solution to, because it keeps popping up
>>  every few months (in slightly different contexts), and it's
>>  going to drive us all nuts.
>
>...which is odd because releases have come with mtree files for
>quite a few years now, and they contain all the information
>necessary to compute the set difference between two arbitrary
>releases.  It wouldn't take too much programming to add a flag
>to mtree(8) which implements ...

That's kind of where I was heading with one of the solutions I
tried to implement, but I am pretty much ignorant of the mtree
files.  Do they really contain a list of all files?  I thought
it was just a directory list.

Also, would this work for people tracking -stable or -current on
a periodic basis?  Ie, are the files up-to-date for every
buildworld, or are they only complete and correct at release
points?

Do the mtree files reflect options the administrator has set when
doing a buildworld, things like NO_KERBEROS or NO_PERL or NO_GAMES,
etc, etc?

-- 
Garance Alistair Drosehn            =   gad_at_gilead.netel.rpi.edu
Senior Systems Programmer           or  gad_at_freebsd.org
Rensselaer Polytechnic Institute    or  drosih_at_rpi.edu