| 1 |
On 03/23/2017 04:22 PM, Alexis Ballier wrote: |
| 2 |
> |
| 3 |
> Indeed, according to pms.git commit log, the rule was laxed because it |
| 4 |
> was clearly an oversight in EAPI6 [1] and was the standard behavior in |
| 5 |
> previous EAPIs. But in the same commit, an "harmless note" was added |
| 6 |
> that "Ebuilds must not access the directory in global scope." in |
| 7 |
> addition to the "May or may not exist" statement and "Not necessarily |
| 8 |
> present when installing from a binary package" footnote. Please explain |
| 9 |
> how this last addition is not a backwards-breaking change. PMS is not a |
| 10 |
> tool to push your personal agenda of cleaning up the deve^^err tree. |
| 11 |
> |
| 12 |
> |
| 13 |
> [1] |
| 14 |
> https://gitweb.gentoo.org/proj/pms.git/commit/?id=fa4ac9474048ec75af138fc61f22485c06aac5b7 |
| 15 |
> |
| 16 |
|
| 17 |
Read that diff again. Before the commit, FILESDIR was invalid in global |
| 18 |
scope (only valid in src_*). This commit makes it valid in global scope, |
| 19 |
but adds the "... don't access it there" clause. |
| 20 |
|
| 21 |
It's not a breaking change because any behavior affected by the clause |
| 22 |
was already illegal before the commit. |
Archives