| 1 |
On 16 Jan 2018 23:32, Mike Gilbert wrote: |
| 2 |
> On Tue, Jan 16, 2018 at 4:46 PM, Mike Frysinger wrote: |
| 3 |
> > Some ebuilds are a bit hard to fix their use of the network in src |
| 4 |
> > phases, so allow them to disable things. This allows us to turn off |
| 5 |
> > access by default and for the vast majority while we work out how to |
| 6 |
> > fix the few broken packages. |
| 7 |
> |
| 8 |
> If we are going to allow network sandboxing to be disabled in |
| 9 |
> individual ebuilds, we should also allow the other sandboxes to be |
| 10 |
> disabled for the same reasons. sys-apps/sandbox has been notoriously |
| 11 |
> buggy, for example. |
| 12 |
|
| 13 |
that sandbox can already be disabled dynamically in ebuilds as needed. |
| 14 |
i don't really see a reason for it to be a RESTRICT value. |
| 15 |
-mike |
Archives