Yes, a generic INSTALL_PROTECT sounds good. I'd vote for that :) It should be used at the final merge stage and not before.
For performance reasons it could be also used at the untar stage when using .tbz2 packages (with --exclude=FILE). On Fri, Oct 24, 2003 at 01:08:13AM +0200, Spider wrote: > On Thu, 23 Oct 2003 23:34:10 +0200 > [EMAIL PROTECTED] (Bj�rn Lindstr�m) wrote: > > > > And why couldn't those lines check the INSTALL_PROTECT (if that's what > > we'll call it) variable? Including the non-installed files in binary > > packages would work doesn't really have anything to do with whether > > this is implemented as a FEATURE flag or a separate variable. > > > > True, and then we could do some interesting default masking, like > walling off /usr/local per default... > -- [EMAIL PROTECTED] mailing list
