| 1 |
On Thu, 23 Mar 2017 21:22:54 +0100 |
| 2 |
Alexis Ballier <aballier@g.o> wrote: |
| 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 |
| 9 |
> explain how this last addition is not a backwards-breaking change. |
| 10 |
> PMS is not a tool to push your personal agenda of cleaning up the |
| 11 |
> deve^^err tree. |
| 12 |
|
| 13 |
The original wording should probably have been something like "may or |
| 14 |
may not exist, so ebuilds MUST NOT go poking around for it", but the |
| 15 |
original wording was written assuming reasonable behaviour from |
| 16 |
developers, and we deliberately chose not to go the SHALL, MUST NOT |
| 17 |
route because of the added cost of developing a specification that's |
| 18 |
safe from hostile implementers. |
| 19 |
|
| 20 |
-- |
| 21 |
Ciaran McCreesh |
Archives