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