From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] What features should be included in EAPI 2?
Date: Wed, 13 Aug 2008 14:02:52 -0700 [thread overview]
Message-ID: <48A34BFC.8060602@gentoo.org> (raw)
In-Reply-To: <20080813130329.0fe55b90@googlemail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ciaran McCreesh wrote:
> On Wed, 13 Aug 2008 01:18:33 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
>> * The old src_compile phase function is split into separate
>> src_configure and src_compile fuctions.
>
> If you're doing new phases... Exheres has been using src_prepare, after
> src_unpack, to avoid having lots of things of the form:
>
> src_unpack() {
> default
> patch blah
> eautoreconf
> }
>
Thanks, that seems like a useful extension.
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkijS/sACgkQ/ejvha5XGaMj4gCfVkfggl6JCAIW9JJkT3Izt9Hr
T3oAoI3RIMTnpaZXxebZhfjZspHhhb/j
=6Wzp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-13 21:02 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 [this message]
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
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=48A34BFC.8060602@gentoo.org \
--to=zmedico@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