On pon, 2017-03-20 at 18:01 +0100, Alexis Ballier wrote: > What makes me wonder more are the proposed solutions: So far the only > proposals I've seen are either inlining *all* the code or moving *all* > the code into an eclass. Having a quick look at autoconf, it seems to me > an intermediate solution would work perfectly fine for the above > goals/rules: Put main.eblit into an eclass. The loading code then would > access $FILESDIR only in src_* phases. This would likely work better > for all parties and would allow to focus on better specifying this gray > area of PMS instead.
Don't you find it a bad hypocritical that at the same time you oppose committing an eclass for a single package and you support committing an eclass to support half-working hack for a single package? -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part