public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild Generators
Date: Wed, 12 Feb 2020 07:36:46 +0800	[thread overview]
Message-ID: <87lfp8k86p.fsf@gentoo.org> (raw)
In-Reply-To: <CA+G3_PP_BCegp-C6Bnjk6guX7f4sE2=cjFs2NT1YLu-LLM2HPw@mail.gmail.com> (Tom Gillespie's message of "Tue, 11 Feb 2020 07:18:44 -0800")

Tom Gillespie <tgbugs@gmail.com> writes:

> For historical curiosity there was also
> https://github.com/domenkozar/g-pypi at one point (similar to
> https://github.com/rafaelmartins/g-octave). Having used g-octave, the
> primary issue is as Michał says, there are a lot of corner cases that
> the generation doesn't handle correctly which lead to broken ebuilds
> and maintenance headaches. Speaking for python, catching and
> correcting the use of setup_requires and other insanity visited upon
> us by the wonders of setuptools makes this a non-starter. 

Yes, I agree.

> If you have a set a known sane packages you could in theory write an
> eclass that captures the regularities of those packages, but I'm not
> sure eclasses are suggested for that use case.

eclass is designed for eliminating duplicated code in ebuilds. Therefore
yes, it is the legitimate use of eclass.

Benda

  reply	other threads:[~2020-02-11 23:36 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
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 [this message]
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=87lfp8k86p.fsf@gentoo.org \
    --to=heroxbd@gentoo.org \
    --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