-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 05 Oct 2008 10:11:08 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> They can call 'die' in global scope. Perhaps it's not the nicest
>> thing to do, but it can be done.
>
> Last time I tried it, Portage behaved rathe
On Sun, 05 Oct 2008 10:11:08 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> They can call 'die' in global scope. Perhaps it's not the nicest
> thing to do, but it can be done.
Last time I tried it, Portage behaved rather horribly with global scope
dies. Is this still the case?
> Considering that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 5 Oct 2008 17:07:40 +0200
> Alexis Ballier <[EMAIL PROTECTED]> wrote:
>> Maybe eclasses should die on unknown eapi; the fact is I really hate
>> the current way it's done when switching an ebuild to EAPI-2 which
>> uses
On Sun, 5 Oct 2008 17:38:11 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> > By the way, do we really want to special case eapi-2 in every
> > eclass ? That's lot of code duplication and will get even worse
> > when we'll reach eapi-42. That would have been cool to have a pm
> > function that te
> On Sun, 5 Oct 2008, Alexis Ballier wrote:
> Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
>> Export it if and only if EAPI is 2.
> By the way, do we really want to special case eapi-2 in every eclass ?
> That's lot of code duplication and will get even worse when we'll reach
> eapi-42. That wo
On Sun, 5 Oct 2008 17:07:40 +0200
Alexis Ballier <[EMAIL PROTECTED]> wrote:
> Maybe eclasses should die on unknown eapi; the fact is I really hate
> the current way it's done when switching an ebuild to EAPI-2 which
> uses an eclass that exports src_compile; most eclasses don't special
> case eapi-
On Sun, 5 Oct 2008 15:24:20 +0100
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Oct 2008 16:15:46 +0200
> Alexis Ballier <[EMAIL PROTECTED]> wrote:
> > An eapi.eclass with such functions and lists of eapi & features
> > maintained there could help though.
>
> The problem is, 'features' c
On Sun, 5 Oct 2008 16:15:46 +0200
Alexis Ballier <[EMAIL PROTECTED]> wrote:
> An eapi.eclass with such functions and lists of eapi & features
> maintained there could help though.
The problem is, 'features' change between EAPIs. For example, all three
EAPIs have src_compile, but it does different
On Sun, 5 Oct 2008 15:07:27 +0100
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Oct 2008 15:36:30 +0200
> Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> > How should exporting of src_configure in eclasses be handled? Should
> > it be conditional, depending on the EAPI? Or is it O.K. to expor
On Sun, 5 Oct 2008 15:36:30 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> How should exporting of src_configure in eclasses be handled? Should
> it be conditional, depending on the EAPI? Or is it O.K. to export
> src_configure unconditionally, since it doesn't harm for EAPI<2?
Export it if and
How should exporting of src_configure in eclasses be handled? Should
it be conditional, depending on the EAPI? Or is it O.K. to export
src_configure unconditionally, since it doesn't harm for EAPI<2?
A concrete example is elisp.eclass which should export an empty
elisp_src_configure function for E
11 matches
Mail list logo
