On Sat, Sep 16, 2006 at 11:02:06PM +0100, Ciaran McCreesh wrote: > On Sat, 16 Sep 2006 00:17:21 -0700 Brian Harring <[EMAIL PROTECTED]> > wrote: > | On Mon, Sep 11, 2006 at 11:22:11PM +0100, Ciaran McCreesh wrote: > | > Protected locations are determined by the ``CONFIG_PROTECT`` > | > environment variable, which is defined in the profiles and which > | > may be augmented or overridden by the current environment and user > | > configuration files. > | > | The user env override has no relevance to ebuilds relying on it, thus > | doesn't have any business being mandated imo (it's implementation > | choice, not requirement of ebuilds). > > Hrm, so installing env.d files that set CONFIG_PROTECT isn't reliable?
Suspect you missed my point- "Overriden by the current environment", aka the users environment at the time of executing $PKG_MANAGER). To build configurationm, portage stacks a bunch of mappings- the last one is the environment the script was ran in. In other words, CONFIG_PROTECT='' emerge blah # does disable CONFIG_PROTECT Portage allows CONFIG_PROTECT from the user env to override; that doesn't mean it's required for CONFIG_PROTECT support, which was the point. ~harring
pgpEVkWjQkpmR.pgp
Description: PGP signature
