>>>>> On Mon, 20 Mar 2017, 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.
But is it desirable as a goal, that all packages in the tree use regular eclasses, but two packages (autoconf and glibc) use something else that is a "grey area"? Also, can somebody please point me to the discussion that preceded the introduction of eblits. AFAICS they appeared sometime in 2007, but I cannot find anything in our mailing list archives. Ulrich
pgp694x4vI54w.pgp
Description: PGP signature
