[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] deprecation of SANDBOX_DISABLED
From:       Brian Harring <ferringb () gentoo ! org>
Date:       2005-09-28 8:05:35
Message-ID: 20050928080535.GK30337 () nightcrawler
[Download RAW message or body]

Hola.

Subject says it all; SANDBOX_DISABLED functions as (essentially) 
RESTRICT="sandbox", except sandbox is left on for pkg_setup .

This is pretty much redundant, considering it's usage.  People stick 
it in the global scope; if you _must_ turn off the sandbox for a 
specific phase, use SANDBOX_ON=0/1 instead.  If you need to disable 
sandbox across the board, restrict="sandbox" is your friend.

Since there are still ebuilds in the tree that would be schmooked by 
it, it's not going to hit in the coming version, but I'd expect it to 
be dead next version after unless people have a really good reason why 
it should live on.

So... thoughts?  Yes it's minor, but it's a matter of cleaning 
up/simplifying portage code, and removing redundancy.
~harring

[Attachment #3 (application/pgp-signature)]
-- 
gentoo-dev@gentoo.org mailing list


[prev in list] [next in list] [prev in thread] [next in thread]