1 |
On Wed, 2014-01-29 at 09:58 +0100, Jan Matejka wrote: |
2 |
> What's the point of having nonempty XDG_ variables in ebuilds? |
3 |
|
4 |
One big reason is FEATURES=test. Test suites for freedesktop-compliant |
5 |
programs that actually run the program are likely to fail if XDG_* |
6 |
directories are resolved as something unwriteable. |
7 |
|
8 |
Also, many gnome-related packages have a build system that won't work if |
9 |
XDG_* variables are wrong. Python packages that use sphinx to generate |
10 |
API docs at build time will hit a sandbox violation if XDG_CONFIG_HOME |
11 |
is unwriteable, see https://bugs.gentoo.org/show_bug.cgi?id=499068 |
12 |
I would be astonished if some packages for kde, xfce, and other desktop |
13 |
environments are not affected as well. |