From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x-modular.eclass: A modified approach to EAPI support
Date: Sun, 08 Mar 2009 15:38:52 -0700 [thread overview]
Message-ID: <49B448FC.6060104@gentoo.org> (raw)
In-Reply-To: <200903081038.44519.levertond@googlemail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Leverton wrote:
> On Sunday 08 March 2009 05:22:03 Donnie Berkholz wrote:
>> FYI, using EXPORT_FUNCTIONS before inherit, as this patch caused
>> x-modular.eclass to do, is broken in current portage releases. Zac said
>> he would change this to be consistent with the lack of any ordering
>> restriction in the PMS. Thanks to Tomáš Chvátal for tracking down this
>> tricky bug!
>
> Better to ask for PMS to be clarified. All existing package managers do
> EXPORT_FUNCTIONS in more or less the same way, so changing it shouldn't
> happen without an EAPI bump.
As discussed on irc, if we make it conditional on EAPI then you'll
practically never be able to call EXPORT_FUNCTIONS before inherit
since eclasses generally support multiple EAPIs. So, I've added a
warning message that is triggered when EXPORT_FUNCTIONS is called
before inherit. In a year or two we can consider having the warning
removed.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAkm0SPsACgkQ/ejvha5XGaN/+ACgsS44TWTR2fODGzwSI0XH5xN7
xpkAoOJhSWeXQDnhO8OuoXuViB2MNe7F
=RJI6
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-03-08 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 20:57 [gentoo-dev] x-modular.eclass: A modified approach to EAPI support Donnie Berkholz
2009-03-06 21:37 ` [gentoo-dev] " Christian Faulhammer
2009-03-06 22:33 ` [gentoo-dev] " Petteri Räty
2009-03-07 7:58 ` Rémi Cardona
2009-03-07 9:50 ` Ulrich Mueller
2009-03-07 10:06 ` Nirbheek Chauhan
2009-03-08 20:23 ` Alistair Bush
2009-03-08 5:22 ` Donnie Berkholz
2009-03-08 10:38 ` David Leverton
2009-03-08 22:38 ` Zac Medico [this message]
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=49B448FC.6060104@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