-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Zac Medico wrote:
| Hello again,
|
| I'd like to get some feedback about what people would like to have
| in the final EAPI 2. In planning for this EAPI bump, we should
| strike a balance somewhere in between everything that we'd like to
| have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello again,
I'd like to get some feedback about what people would like to have
in the final EAPI 2. In planning for this EAPI bump, we should
strike a balance somewhere in between everything that we'd like to
have and whatever we can implement in a
On Wed, 13 Aug 2008 01:18:33 -0700
Zac Medico [EMAIL PROTECTED] 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
Zac Medico kirjoitti:
* Default phase function implementations for older EAPIs are
accessible via functions having names that start with 'eapi',
followed by the EAPI value.
What's the benefit of this feature?
Regards,
Petteri
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
On Wed, 13 Aug 2008 01:18:33 -0700
Zac Medico [EMAIL PROTECTED] 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Petteri Räty wrote:
Zac Medico kirjoitti:
* Default phase function implementations for older EAPIs are
accessible via functions having names that start with 'eapi',
followed by the EAPI value.
What's the benefit of this feature?
In
Zac Medico kirjoitti:
Petteri Räty wrote:
Zac Medico kirjoitti:
* Default phase function implementations for older EAPIs are
accessible via functions having names that start with 'eapi',
followed by the EAPI value.
What's the benefit of this feature?
In some cases it might be
