| 1 |
On Sat, Jan 25, 2014 at 4:16 PM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> Dnia 2014-01-25, o godz. 11:13:38 |
| 3 |
> Mike Gilbert <floppym@g.o> napisał(a): |
| 4 |
> |
| 5 |
>> It seems having XDG variables like XDG_CONFIG_HOME set in the |
| 6 |
>> environment when calling emerge has a tendency to cause sandbox |
| 7 |
>> violations. For example, see the bugs blocking bug 499202. |
| 8 |
>> |
| 9 |
>> https://bugs.gentoo.org/show_bug.cgi?id=499202 |
| 10 |
>> |
| 11 |
>> If you grep for XDG_CONFIG_HOME in the eclass directory, you can see |
| 12 |
>> that several eclasses work around this by setting |
| 13 |
>> XDG_CONFIG_HOME="${T}" or "${T}/.config". |
| 14 |
>> |
| 15 |
>> gnome2-utils.eclass takes it a step further and creates empty |
| 16 |
>> directories for several other XDG variables. |
| 17 |
>> |
| 18 |
>> Is this something we can/should consolidate into some central place? |
| 19 |
>> Or should I just copy/paste something into distutils-r1.eclass? |
| 20 |
> |
| 21 |
> I'd say portage should kill that as part of sanitizing the environment. |
| 22 |
> There's no point in reproducing it in random eclasses. |
| 23 |
> |
| 24 |
|
| 25 |
I have filed an enhancement request for Portage. |
| 26 |
|
| 27 |
https://bugs.gentoo.org/show_bug.cgi?id=499288 |
Archives