1 |
Dnia 2014-01-26, o godz. 21:35:27 |
2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> napisał(a): |
3 |
|
4 |
> On Sun, 26 Jan 2014 13:21:44 -0800 |
5 |
> Alec Warner <antarus@g.o> wrote: |
6 |
> > Sorry, I work on Portage. What I'm saying is that We are free to |
7 |
> > change the behavior of *portage* now; rather than waiting for a new |
8 |
> > EAPI. If an ebuild needs to define EAPI=eapi-next to 'correctly' use |
9 |
> > XDG_*, well that is someone else's can of worms. |
10 |
> |
11 |
> Changing Portage to hide the issue is a bad idea, since it makes it |
12 |
> harder for developers to notice that that's a problem they need to fix. |
13 |
> Although maybe you could set XDG_* to something that will give a big |
14 |
> noisy sandbox violation for current EAPIs? |
15 |
|
16 |
Yes, because instantly breaking a few dozen ebuilds in stable tree for |
17 |
the sake of proving a point is always a good idea. |
18 |
|
19 |
-- |
20 |
Best regards, |
21 |
Michał Górny |