1 |
On Thu, 2017-03-23 at 22:42 +0100, Alexis Ballier wrote: |
2 |
> On Thu, 23 Mar 2017 17:20:59 -0400 |
3 |
> Michael Orlitzky <mjo@g.o> wrote: |
4 |
> |
5 |
> > On 03/23/2017 04:22 PM, Alexis Ballier wrote: |
6 |
> > > |
7 |
> > > Indeed, according to pms.git commit log, the rule was laxed |
8 |
> > > because |
9 |
> > > it was clearly an oversight in EAPI6 [1] and was the standard |
10 |
> > > behavior in previous EAPIs. But in the same commit, an "harmless |
11 |
> > > note" was added that "Ebuilds must not access the directory in |
12 |
> > > global scope." in addition to the "May or may not exist" |
13 |
> > > statement |
14 |
> > > and "Not necessarily present when installing from a binary |
15 |
> > > package" |
16 |
> > > footnote. Please explain how this last addition is not a |
17 |
> > > backwards-breaking change. PMS is not a tool to push your |
18 |
> > > personal |
19 |
> > > agenda of cleaning up the deve^^err tree. |
20 |
> > > |
21 |
> > > |
22 |
> > > [1] |
23 |
> > > https://gitweb.gentoo.org/proj/pms.git/commit/?id=fa4ac9474048ec7 |
24 |
> > > 5af138fc61f22485c06aac5b7 |
25 |
> > > |
26 |
> > |
27 |
> > Read that diff again. Before the commit, FILESDIR was invalid in |
28 |
> > global scope (only valid in src_*). This commit makes it valid in |
29 |
> > global scope, but adds the "... don't access it there" clause. |
30 |
> > |
31 |
> > It's not a breaking change because any behavior affected by the |
32 |
> > clause was already illegal before the commit. |
33 |
> |
34 |
> |
35 |
> If we were to stop thinking and follow the rule by the letter: What |
36 |
> are |
37 |
> we waiting for to file bugs for every package having ${FILESDIR} |
38 |
> somewhere in global scope then ? |
39 |
> After all, those are the council approved versions and EAPIs cannot |
40 |
> change. |
41 |
> |
42 |
> Or you can read again the first sentence in the part you quoted. |
43 |
> |
44 |
|
45 |
https://bugs.gentoo.org/show_bug.cgi?id=586416 |