| 1 |
El sáb, 25-01-2014 a las 11:13 -0500, Mike Gilbert escribió: |
| 2 |
> It seems having XDG variables like XDG_CONFIG_HOME set in the |
| 3 |
> environment when calling emerge has a tendency to cause sandbox |
| 4 |
> violations. For example, see the bugs blocking bug 499202. |
| 5 |
> |
| 6 |
> https://bugs.gentoo.org/show_bug.cgi?id=499202 |
| 7 |
> |
| 8 |
> If you grep for XDG_CONFIG_HOME in the eclass directory, you can see |
| 9 |
> that several eclasses work around this by setting |
| 10 |
> XDG_CONFIG_HOME="${T}" or "${T}/.config". |
| 11 |
> |
| 12 |
> gnome2-utils.eclass takes it a step further and creates empty |
| 13 |
> directories for several other XDG variables. |
| 14 |
> |
| 15 |
> Is this something we can/should consolidate into some central place? |
| 16 |
> Or should I just copy/paste something into distutils-r1.eclass? |
| 17 |
> |
| 18 |
|
| 19 |
Maybe the function cleaning stuff could be added to eutils.eclass and we |
| 20 |
would call it from other eclasses/ebuilds. I also wonder if this cleanup |
| 21 |
could be done always in a newer eapi since we usually need to add that |
| 22 |
fix whenever we suffer the sandbox violation :S (not before) |
Archives