>>>>> On Sat, 16 Aug 2014, William Hubbs wrote: > The initial proposal is to change this behaviour so that the PMS > default phase functions call all matching phase functions from > inherited eclasses in sequence.
> I strongly oppose this change, because I feel it will make our > entire tree very unpredictable at best. [...] +1 > My counter proposal to this is that we stop calling eclass phase > functions automatically, and to minimize the amount of boilerplating > we would have to do, we use a variable, such as ECLASS_PHASES which > would be defined at the ebuild level and contain a list of the > eclass phase functions we want to run automatically. I'm strongly opposed against this proposal, too. Our current system essentially works. Also, already now you can suppress automatic calling of phase functions at the eclass level (by not exporting them) and at the ebuild level (by defining explicit phase functions). Ulrich
pgp9hPgomevPD.pgp
Description: PGP signature
