public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x-modular.eclass: A modified approach to EAPI support
Date: Sat, 07 Mar 2009 00:33:24 +0200	[thread overview]
Message-ID: <49B1A4B4.1000804@gentoo.org> (raw)
In-Reply-To: <20090306205729.GC22566@comet>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

Donnie Berkholz wrote:
> I decided to try something a little different because I had some ideas 
> for improving the existing EAPI patches I've seen going into other 
> eclasses. So here is my patch for x-modular.eclass. I tested it with 
> ebuilds using EAPIs 0, 1, and 2, and it appeared to work fine. It 
> already happened to have a function called src_configure, so that 
> doesn't appear in the patch.
> 
> One thing I see as an improvement is a lack of EAPI value checks 
> throughout the ebuild to avoid repetition between the function export 
> and the function call. Things just check whether a function was 
> exported, which is the only place where EAPI value checks happen.
> 
> Additionally, the fallback in case statements is "I don't know what to 
> do" and supported EAPIs are explicitly defined. This will make it 
> obvious when the eclass doesn't support a new EAPI instead of it 
> randomly failing after you try it.
> 
> Any thoughts?
> 
> 

The other option instead of die would be DEPEND="THIS-IS-NOT-VALID".

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]

  parent reply	other threads:[~2009-03-06 22:32 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 ` Petteri Räty [this message]
2009-03-07  7:58 ` [gentoo-dev] " 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

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=49B1A4B4.1000804@gentoo.org \
    --to=betelgeuse@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