| 1 |
On 05/29/2012 04:22 PM, Richard Yao wrote: |
| 2 |
> On 05/29/12 18:11, Zac Medico wrote: |
| 3 |
>> On 05/29/2012 02:47 PM, Hilco Wijbenga wrote: |
| 4 |
>>> On 29 May 2012 12:46, Michael Orlitzky <michael@××××××××.com> wrote: |
| 5 |
>>>> How about introducing e.g. FEATURES="nouserpriv", and make the current |
| 6 |
>>>> userpriv behavior the default? |
| 7 |
>>> |
| 8 |
>>> rootpriv instead of nouserpriv? |
| 9 |
>> |
| 10 |
>> What's the use case for this? Can't we just enable userpriv |
| 11 |
>> unconditionally, so that it doesn't have to be listed in FEATURES? Note |
| 12 |
>> that ebuilds will still be able to use RESTRICT=userpriv if necessary. |
| 13 |
> |
| 14 |
> Would FEATURES=-userpriv still work at the command line? It could be |
| 15 |
> useful for debugging to keep that working. |
| 16 |
|
| 17 |
Yeah, I guess it would be bad for it to be unconditional, because |
| 18 |
permission issues seem to be a really common source of trouble for |
| 19 |
people. Even something as seemingly simple as userfetch probably |
| 20 |
shouldn't be unconditional, due to issues like the ACLs discussed in bug |
| 21 |
#416705 [1]. |
| 22 |
|
| 23 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=416705 |
| 24 |
-- |
| 25 |
Thanks, |
| 26 |
Zac |
Archives