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