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
pgpWyUB9DfcVy.pgp
Description: PGP signature
