| 1 |
On Mon, 20 Mar 2017 20:25:52 +0100 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
|
| 4 |
> >>>>> On Mon, 20 Mar 2017, Alexis Ballier wrote: |
| 5 |
> |
| 6 |
> > What makes me wonder more are the proposed solutions: So far the |
| 7 |
> > only proposals I've seen are either inlining *all* the code or |
| 8 |
> > moving *all* the code into an eclass. Having a quick look at |
| 9 |
> > autoconf, it seems to me an intermediate solution would work |
| 10 |
> > perfectly fine for the above goals/rules: Put main.eblit into an |
| 11 |
> > eclass. The loading code then would access $FILESDIR only in src_* |
| 12 |
> > phases. This would likely work better for all parties and would |
| 13 |
> > allow to focus on better specifying this gray area of PMS instead. |
| 14 |
> |
| 15 |
> But is it desirable as a goal, that all packages in the tree use |
| 16 |
> regular eclasses, but two packages (autoconf and glibc) use something |
| 17 |
> else that is a "grey area"? |
| 18 |
|
| 19 |
No. Unless I've missed something, in which case please point it out, |
| 20 |
main.eblit is generic enough to be an eclass and if called only from |
| 21 |
src_* phases, it gets the whole thing out of this grey area. |
Archives