From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] What features should be included in EAPI 2?
Date: Tue, 19 Aug 2008 19:18:04 +0100 [thread overview]
Message-ID: <20080819191804.19c67b0a@googlemail.com> (raw)
In-Reply-To: <48AB0A6D.6050705@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
On Tue, 19 Aug 2008 23:31:17 +0530
Arun Raghavan <ford_prefect@gentoo.org> wrote:
> Ciaran McCreesh wrote:
> > The benefit is that it's a logically separate action, and will avoid
> > all the silliness of people repeatedly changing their minds about
> > which phase should do the eautoreconf calls and so on.
>
> a) Is this really an issue for maintainers?
It's not a huge issue, any more than src_configure is. Equally, it's not
expensive to implement.
> b) Does it really matter?
In the grand scheme of things, no. In the grand scheme of things, you
only *need* a single src_ function. From a maintainer convenience
perspective, however, src_prepare is marginally more useful than having
a split src_configure.
> c) So the flow will look like:
>
> ...
> src_unpack
> src_prepare
> src_configure
> src_compile
> ...
>
> To me this seems like an unnecessary overgeneralisation.
It's a better mapping of the things ebuilds do than the current set of
functions.
The logic is this: lots of ebuilds end up duplicating src_unpack (or,
in future EAPIs, calling 'default') and then adding things to do
preparation work. Experience suggests that the most common reason for
overriding src_unpack is to do preparation work, not to change how
things are unpacked.
(Number-wise... For Exherbo, where the split's already been made,
custom src_prepare functions are three times more common than custom
src_unpack functions. And that figure's significantly lower than what
Gentoo would see, because with exheres-0 'default' functions you don't
need to write a src_prepare if you're merely applying patches.)
> The *only* potential "benefit" I see here is that at some point of
> time in the nebulous future, it might be possible to tell the PM to
> always skip src_prepare in order to give a system where everything is
> "vanilla".
Such a system wouldn't be usable... Not all of Gentoo's patches are
non-essential.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-19 18:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 8:18 [gentoo-dev] [RFC] What features should be included in EAPI 2? Zac Medico
2008-08-13 12:03 ` Ciaran McCreesh
2008-08-13 21:02 ` Zac Medico
2008-08-19 11:12 ` [gentoo-dev] " Steve Long
2008-08-19 12:45 ` Ciaran McCreesh
2008-08-19 18:01 ` Arun Raghavan
2008-08-19 18:18 ` Ciaran McCreesh [this message]
2008-08-19 20:27 ` [gentoo-dev] " Steve Long
2008-08-19 20:43 ` Ciaran McCreesh
2008-08-21 15:35 ` [gentoo-dev] " Steve Long
2008-08-21 15:58 ` Ciaran McCreesh
2008-08-22 2:26 ` Alec Warner
2008-08-23 14:15 ` [gentoo-dev] " Steve Long
2008-09-01 14:31 ` [gentoo-dev] " Peter Volkov
2008-08-27 3:15 ` [gentoo-dev] " Ryan Hill
2008-08-21 17:37 ` Thomas Anderson
2008-08-13 20:28 ` [gentoo-dev] " Petteri Räty
2008-08-13 21:07 ` Zac Medico
2008-08-13 22:55 ` Petteri Räty
2008-08-25 20:03 ` Jorge Manuel B. S. Vicetto
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=20080819191804.19c67b0a@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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