On Thu, 23 Mar 2017 22:45:54 +0100 David Seifert <s...@gentoo.org> wrote:
> On Thu, 2017-03-23 at 22:42 +0100, Alexis Ballier wrote: > > On Thu, 23 Mar 2017 17:20:59 -0400 > > Michael Orlitzky <m...@gentoo.org> wrote: > > > > > On 03/23/2017 04:22 PM, Alexis Ballier wrote: > > > > > > > > Indeed, according to pms.git commit log, the rule was laxed > > > > because > > > > it was clearly an oversight in EAPI6 [1] and was the standard > > > > behavior in previous EAPIs. But in the same commit, an "harmless > > > > note" was added that "Ebuilds must not access the directory in > > > > global scope." in addition to the "May or may not exist" > > > > statement > > > > and "Not necessarily present when installing from a binary > > > > package" > > > > footnote. Please explain how this last addition is not a > > > > backwards-breaking change. PMS is not a tool to push your > > > > personal > > > > agenda of cleaning up the deve^^err tree. > > > > > > > > > > > > [1] > > > > https://gitweb.gentoo.org/proj/pms.git/commit/?id=fa4ac9474048ec7 > > > > 5af138fc61f22485c06aac5b7 > > > > > > > > > > Read that diff again. Before the commit, FILESDIR was invalid in > > > global scope (only valid in src_*). This commit makes it valid in > > > global scope, but adds the "... don't access it there" clause. > > > > > > It's not a breaking change because any behavior affected by the > > > clause was already illegal before the commit. > > > > > > If we were to stop thinking and follow the rule by the letter: What > > are > > we waiting for to file bugs for every package having ${FILESDIR} > > somewhere in global scope then ? > > After all, those are the council approved versions and EAPIs cannot > > change. > > > > Or you can read again the first sentence in the part you quoted. > > > > https://bugs.gentoo.org/show_bug.cgi?id=586416 > yep, that's about tracking access to the dir not to the variable itself
