From: Gerion Entrup <gerion.entrup@flump.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild Generators (Was: GSoC 2020: Call for mentors and project ideas)
Date: Mon, 03 Feb 2020 10:42:08 +0100 [thread overview]
Message-ID: <4207106.LvFx2qVVIh@falbala> (raw)
In-Reply-To: <87sgjs5mjp.fsf_-_@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]
Am Montag, 3. Februar 2020, 05:20:42 CET schrieb Benda Xu:
> Gerion Entrup <gerion.entrup@flump.de> writes:
>
> > I saw the idea „Big Data Infrastructure by Gentoo“ and found it kind of
> > interesting. However, I have a little bit the fear that a full automation
> > won't be possible and the whole project becomes a little bit like g-sorcery
> > (gs-pypi, gs-elpa) or g-octave: a really cool project but not used at a
> > large scale.
>
> Yes, that's true. I share the same observation and concern with you.
>
> This is one exception: the CRAN ebuild generator powered R overlay has
> been running well for 8 years.
>
> https://wiki.gentoo.org/wiki/Project:Science/Overlay/R
Hmm, interesting, thank you.
> > What do you think of the idea to not do this fully automated but supervised
> > by a maintainer? With that I mean an ebuild generator that generates only
> > the parts of the ebuild that it can easily parse and then present the ebuild
> > draft to a maintainer who completes it to an full ebuild. As far a I know no
> > tool like this exists. I think the focus shift helps a lot:
> > Developing a tool for the Gentoo maintainer not the Gentoo user.
>
> Yes, that makes a lot of sense. The R overlay follows this model. Most
> of the ebuilds are automated. When an ebuild generation fails, we add
> the ebuild manually, understand it and then update the generator to
> cover it in the future.
Is this possible in all cases? I think of adding custom patches,
appropriate mapping of dependencies, check for things like desktop icon
cache...
> > I'm only "maintaining" an overlay so maybe I'm missing experience
> > but I often have wished a tool that automatically parses the language specific
> > packaging files and is able to generate a primitive ebuild out of that.
> > Maybe it even can do this in an interactive way:
> > "Hey, upstream needs the dependency 'foo'. In the Gentoo packages I have found
> > 'dev-bar/foo' and 'dev-util/foo'. What is the correct one?"
>
> Yes, that's the way R overlay is working. And I have a similar plan and
> proof-of-concept solution for the Java Maven overlay.
Nice to hear. I think, it is meaningful to solve all generation with one
tool. Maybe it can even "recognize" the used build system and package
database. Is this your plan, too?
Best,
Gerion
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2020-02-03 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 16:00 [gentoo-dev] GSoC 2020: Call for mentors and project ideas alicef
2020-01-25 12:53 ` Benda Xu
2020-02-02 11:47 ` Benda Xu
2020-02-02 16:54 ` Gerion Entrup
2020-02-03 4:20 ` [gentoo-dev] Ebuild Generators (Was: GSoC 2020: Call for mentors and project ideas) Benda Xu
2020-02-03 9:42 ` Gerion Entrup [this message]
2020-02-03 12:19 ` [gentoo-dev] Ebuild Generators Benda Xu
2020-02-03 12:30 ` Michael 'veremitz' Everitt
2020-02-03 13:20 ` Gerion Entrup
2020-02-03 13:26 ` Michał Górny
2020-02-11 15:18 ` Tom Gillespie
2020-02-11 23:36 ` Benda Xu
2020-02-12 7:56 ` Gerion Entrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4207106.LvFx2qVVIh@falbala \
--to=gerion.entrup@flump.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox