1 |
Am Sonntag, 2. Februar 2020, 12:47:55 CET schrieb Benda Xu: |
2 |
> Dear Fellows, |
3 |
> |
4 |
> alicef <alicef@g.o> writes: |
5 |
> |
6 |
> > As always, Gentoo plans to participate in the Google Summer of Code |
7 |
> > 2020. We are looking for new project ideas and are always open for |
8 |
> > new mentors. |
9 |
> > Google Summer of Code is a big opportunity for making Gentoo project more |
10 |
> > visible and get more people interested to join Gentoo and helping out. |
11 |
> > |
12 |
> > [...] |
13 |
> |
14 |
> This year's GSoC organization application deadline is on Feb 5. The |
15 |
> more project ideas, the better Gentoo will show itself to be prepared. |
16 |
> If you have been thinking of adding projects to our GSoC 2020 list, this |
17 |
> is a good chance to do so. |
18 |
> |
19 |
> Cheers, |
20 |
> Benda |
21 |
> |
22 |
|
23 |
Hi, |
24 |
|
25 |
I saw the idea „Big Data Infrastructure by Gentoo“ and found it kind of |
26 |
interesting. However, I have a little bit the fear that a full automation |
27 |
won't be possible and the whole project becomes a little bit like g-sorcery |
28 |
(gs-pypi, gs-elpa) or g-octave: a really cool project but not used at a |
29 |
large scale. |
30 |
|
31 |
What do you think of the idea to not do this fully automated but supervised |
32 |
by a maintainer? With that I mean an ebuild generator that generates only |
33 |
the parts of the ebuild that it can easily parse and then present the ebuild |
34 |
draft to a maintainer who completes it to an full ebuild. As far a I know no |
35 |
tool like this exists. I think the focus shift helps a lot: |
36 |
Developing a tool for the Gentoo maintainer not the Gentoo user. |
37 |
|
38 |
I'm only "maintaining" an overlay so maybe I'm missing experience |
39 |
but I often have wished a tool that automatically parses the language specific |
40 |
packaging files and is able to generate a primitive ebuild out of that. |
41 |
Maybe it even can do this in an interactive way: |
42 |
"Hey, upstream needs the dependency 'foo'. In the Gentoo packages I have found |
43 |
'dev-bar/foo' and 'dev-util/foo'. What is the correct one?" |
44 |
|
45 |
With a not fully automatic tool also packages can be parsed that are not |
46 |
in a complete closed ecosystem, like a 'meson.build' file or cmake files for |
47 |
C++/C programs. But of course package databases like Maven/Cargo/Pypi are |
48 |
also candidates. |
49 |
|
50 |
Unfortunately, I have no time currently to participate in the GSOC. I just |
51 |
want to mention this here as an idea. Please comment or correct me, if |
52 |
such a tool already exists. |
53 |
|
54 |
Best, |
55 |
Gerion |