| 1 |
On 07/02/2012 12:48 PM, Pacho Ramos wrote: |
| 2 |
> El lun, 28-05-2012 a las 14:34 -0700, Zac Medico escribió: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> In case you aren't familiar with FEATURES=userpriv, here's the |
| 6 |
>> description from the make.conf(5) man page: |
| 7 |
>> |
| 8 |
>> Allow portage to drop root privileges and compile packages as |
| 9 |
>> portage:portage without a sandbox (unless usersandbox is also used). |
| 10 |
>> |
| 11 |
>> The rationale for having the separate "usersandbox" setting, to enable |
| 12 |
>> use of sys-apps/sandbox, is that people who enable userpriv sometimes |
| 13 |
>> prefer to have sandbox disabled in order to slightly improve |
| 14 |
>> performance. However, I would recommend to enable usersandbox by |
| 15 |
>> default, for the purpose of logging sandbox violations. |
| 16 |
>> |
| 17 |
>> Note that ebuilds can set RESTRICT="userpriv" if they require superuser |
| 18 |
>> privileges during any of the src_* phases that userpriv affects. |
| 19 |
>> |
| 20 |
>> I've been using FEATURES="userpriv usersandbox" for years, and I don't |
| 21 |
>> remember experiencing any problems because of it, so I think that it |
| 22 |
>> would be reasonable to have it enabled by default. Objections? |
| 23 |
> |
| 24 |
> Looks like non important problems arised and, then, these could probably |
| 25 |
> be enabled by default, no? :) |
| 26 |
|
| 27 |
I'm not sure about the best way to handle migration for directories |
| 28 |
inside $DISTDIR that are used by live ebuilds, since src_unpack will run |
| 29 |
with different privileges when userpriv is enabled. |
| 30 |
-- |
| 31 |
Thanks, |
| 32 |
Zac |
Archives