| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
David Leverton wrote: |
| 5 |
> On Sunday 08 March 2009 05:22:03 Donnie Berkholz wrote: |
| 6 |
>> FYI, using EXPORT_FUNCTIONS before inherit, as this patch caused |
| 7 |
>> x-modular.eclass to do, is broken in current portage releases. Zac said |
| 8 |
>> he would change this to be consistent with the lack of any ordering |
| 9 |
>> restriction in the PMS. Thanks to Tomáš Chvátal for tracking down this |
| 10 |
>> tricky bug! |
| 11 |
> |
| 12 |
> Better to ask for PMS to be clarified. All existing package managers do |
| 13 |
> EXPORT_FUNCTIONS in more or less the same way, so changing it shouldn't |
| 14 |
> happen without an EAPI bump. |
| 15 |
|
| 16 |
As discussed on irc, if we make it conditional on EAPI then you'll |
| 17 |
practically never be able to call EXPORT_FUNCTIONS before inherit |
| 18 |
since eclasses generally support multiple EAPIs. So, I've added a |
| 19 |
warning message that is triggered when EXPORT_FUNCTIONS is called |
| 20 |
before inherit. In a year or two we can consider having the warning |
| 21 |
removed. |
| 22 |
- -- |
| 23 |
Thanks, |
| 24 |
Zac |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2.0.10 (GNU/Linux) |
| 27 |
|
| 28 |
iEYEARECAAYFAkm0SPsACgkQ/ejvha5XGaN/+ACgsS44TWTR2fODGzwSI0XH5xN7 |
| 29 |
xpkAoOJhSWeXQDnhO8OuoXuViB2MNe7F |
| 30 |
=RJI6 |
| 31 |
-----END PGP SIGNATURE----- |
Archives