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