On Wed, 10 Jan 2007 14:00:42 -0500 Mike Frysinger <[EMAIL PROTECTED]> wrote:
> On Wednesday 10 January 2007 13:45, Jakub Moc wrote: > > Real solution, sure... RESTRICT=sandbox is not a solution, it's > > identical to the current hackish workaround, so I guess we can save > > portage folks the trouble... > > except that RESTRICT is the documented method for disabling user > FEATURES in ebuilds ... it works for pretty much every FEATURE except > some -mike Ok, before this myth gets stuck any more: FEATURES and RESTRICT are two independent entities. That *some* FEATURES have a matching RESTRICT value is more a coincidence that a design pattern. Also RESTRICT handles some things that have no matching entry in FEATURES (like the infamous RESTRICT=fetch for example) or have a different meaning than their matching FEATURES value (e.g. RESTRICT=mirror has nothing in common with FEATURES=mirror). Marius PS: this isn't an argument for or against the original proposal. -- [email protected] mailing list
