1 |
Hola. |
2 |
|
3 |
Subject says it all; SANDBOX_DISABLED functions as (essentially) |
4 |
RESTRICT="sandbox", except sandbox is left on for pkg_setup . |
5 |
|
6 |
This is pretty much redundant, considering it's usage. People stick |
7 |
it in the global scope; if you _must_ turn off the sandbox for a |
8 |
specific phase, use SANDBOX_ON=0/1 instead. If you need to disable |
9 |
sandbox across the board, restrict="sandbox" is your friend. |
10 |
|
11 |
Since there are still ebuilds in the tree that would be schmooked by |
12 |
it, it's not going to hit in the coming version, but I'd expect it to |
13 |
be dead next version after unless people have a really good reason why |
14 |
it should live on. |
15 |
|
16 |
So... thoughts? Yes it's minor, but it's a matter of cleaning |
17 |
up/simplifying portage code, and removing redundancy. |
18 |
~harring |