>>>>> On Sun, 29 May 2016, Rich Freeman wrote: > What I would love to see is this be standardized. An eclass or a > GLEP seems like the logical approach.
I am strongly opposed against this. Ebuilds should not source
executable code from random locations. This is also a huge QA
violation, since PMS neither guarantees FILESDIR to be available in
global scope (so especially, not during metadata generation), nor in
any of the pkg_* phases (like pkg_setup, where mips-sources sources
its eblits).
If there really is a need for such a feature, we should rather follow
an approach like the per-package eclasses previously suggested by mabi
and antarus [1], and support a pkg-inherit function in the next EAPI.
(Though I wouldn't add a new function, but add an option to inherit,
like "inherit -p".)
We could even think about per-category eclasses ("inherit -c"),
although it is not obvious where one would store them.
Ulrich
[1]
https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/users/antarus/projects/gleps/glep-XX.txt?view=markup
pgpgha4YdinNO.pgp
Description: PGP signature
