1 |
On 03/20/2017 15:25, Ulrich Mueller wrote: |
2 |
>>>>>> On Mon, 20 Mar 2017, Alexis Ballier wrote: |
3 |
> |
4 |
>> What makes me wonder more are the proposed solutions: So far the |
5 |
>> only proposals I've seen are either inlining *all* the code or |
6 |
>> moving *all* the code into an eclass. Having a quick look at |
7 |
>> autoconf, it seems to me an intermediate solution would work |
8 |
>> perfectly fine for the above goals/rules: Put main.eblit into an |
9 |
>> eclass. The loading code then would access $FILESDIR only in src_* |
10 |
>> phases. This would likely work better for all parties and would |
11 |
>> allow to focus on better specifying this gray area of PMS instead. |
12 |
> |
13 |
> But is it desirable as a goal, that all packages in the tree use |
14 |
> regular eclasses, but two packages (autoconf and glibc) use something |
15 |
> else that is a "grey area"? |
16 |
> |
17 |
> Also, can somebody please point me to the discussion that preceded the |
18 |
> introduction of eblits. AFAICS they appeared sometime in 2007, but I |
19 |
> cannot find anything in our mailing list archives. |
20 |
> |
21 |
> Ulrich |
22 |
|
23 |
I believe the other working name this idea of ebuild code-reuse went under was |
24 |
"elibs". There was a partial GLEP written, enough that it was granted a |
25 |
number, but I forget that number off the top of my head. |
26 |
|
27 |
That said, I think a key problem here is the use of the word "eblit" has become |
28 |
poisoned for various reasons, and this makes the continued use of the term and |
29 |
its current implementation untenable. |
30 |
|
31 |
In general, the concept of code-sharing common blocks of logic between multiple |
32 |
ebuilds in a specific package directory that is not a top-level eclass is not |
33 |
entirely without merit. But the only way this idea can be realized in a |
34 |
suitable manner and be used by far more consumers than today's eblits are, is |
35 |
to either find and finish the old elibs GLEP or start one over from scratch, |
36 |
submit whatever needs submitting via patches to at least PMS and Portage, work |
37 |
through whatever processes are required for approval, and then deploy it in the |
38 |
next EAPI. |
39 |
|
40 |
If anyone is game for working something up or discussing further, let me know. |
41 |
|
42 |
-- |
43 |
Joshua Kinard |
44 |
Gentoo/MIPS |
45 |
kumba@g.o |
46 |
6144R/F5C6C943 2015-04-27 |
47 |
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943 |
48 |
|
49 |
"The past tempts us, the present confuses us, the future frightens us. And our |
50 |
lives slip away, moment by moment, lost in that vast, terrible in-between." |
51 |
|
52 |
--Emperor Turhan, Centauri Republic |