From: Arun Raghavan <ford_prefect@gentoo.org>
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 23:31:17 +0530 [thread overview]
Message-ID: <48AB0A6D.6050705@gentoo.org> (raw)
In-Reply-To: <82dd739f0808190545u3cb1632fj3590a6b130dd304a@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
b) Does it really matter?
c) So the flow will look like:
...
src_unpack
src_prepare
src_configure
src_compile
...
To me this seems like an unnecessary overgeneralisation. 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".
This is not something I see as being useful to us.
- -- Arun
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkirCm0ACgkQ+Vqt1inD4uyTvQCgjEPHRCJUFrIsoyk5EnYb/jNC
Lu8An0KTbHP59UXa4UcShSC7VwLUgQpI
=zwPv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-19 18:01 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 [this message]
2008-08-19 18:18 ` Ciaran McCreesh
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=48AB0A6D.6050705@gentoo.org \
--to=ford_prefect@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