1 |
Hi Gerion, |
2 |
|
3 |
Gerion Entrup <gerion.entrup@×××××.de> writes: |
4 |
|
5 |
>> Yes, that makes a lot of sense. The R overlay follows this model. Most |
6 |
>> of the ebuilds are automated. When an ebuild generation fails, we add |
7 |
>> the ebuild manually, understand it and then update the generator to |
8 |
>> cover it in the future. |
9 |
> |
10 |
> Is this possible in all cases? I think of adding custom patches, |
11 |
> appropriate mapping of dependencies, check for things like desktop |
12 |
> icon cache... |
13 |
|
14 |
That's too complex to handle automatically. Luckily, in R overlay, such |
15 |
packages are less than 5%. An ebuild generator is based on the |
16 |
observation that many language-specific packages are trivial to fetch, |
17 |
compile and install. |
18 |
|
19 |
>> > I'm only "maintaining" an overlay so maybe I'm missing experience |
20 |
>> > but I often have wished a tool that automatically parses the language specific |
21 |
>> > packaging files and is able to generate a primitive ebuild out of that. |
22 |
>> > Maybe it even can do this in an interactive way: |
23 |
>> > "Hey, upstream needs the dependency 'foo'. In the Gentoo packages I have found |
24 |
>> > 'dev-bar/foo' and 'dev-util/foo'. What is the correct one?" |
25 |
>> |
26 |
>> Yes, that's the way R overlay is working. And I have a similar plan and |
27 |
>> proof-of-concept solution for the Java Maven overlay. |
28 |
> |
29 |
> Nice to hear. I think, it is meaningful to solve all generation with one |
30 |
> tool. Maybe it can even "recognize" the used build system and package |
31 |
> database. Is this your plan, too? |
32 |
|
33 |
No, I don't think it possible as far as I can see... That would be a |
34 |
strong AI. |
35 |
|
36 |
Yours, |
37 |
Benda |