public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: hardened glibc and gcc dependencies
Date: Fri, 28 Oct 2011 22:50:08 +0530	[thread overview]
Message-ID: <CADqQcK4x1C7CX5ZA5pO52XhOmYcrLoBZCCjNZTKLOV1siJJexQ@mail.gmail.com> (raw)
In-Reply-To: <4EAA93C4.6030101@gentoo.org>

On Fri, Oct 28, 2011 at 5:06 PM, Anthony G. Basile <blueness@gentoo.org> wrote:
> Approaching this naively, can't we just set EAPI="2" in the eclass, see
> what breaks and fix?  Or is it more involved because some EAPI="0"
> ebuilds would be inheriting it and we'd need  a lot of if "${EAPI}" == 0
> checks interspersed through the eclass?
>

afaik, eclasses aren't supposed to be setting EAPI. They can choose to
not support some EAPIs and error out, but they need checks.

Mostly, eclasses read ${EAPI} to do conditional exporting of phases
and conditional usage of features.


-- 
~Nirbheek Chauhan

Gentoo GNOME+Mozilla Team



  reply	other threads:[~2011-10-28 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  9:03 [gentoo-dev] hardened glibc and gcc dependencies "Paweł Hajdan, Jr."
2011-10-27 16:08 ` "Paweł Hajdan, Jr."
2011-10-27 16:49   ` [gentoo-dev] " Duncan
2011-10-27 17:33   ` [gentoo-dev] " Nirbheek Chauhan
2011-10-27 23:47     ` [gentoo-dev] " Ryan Hill
2011-10-27 23:50       ` Mike Frysinger
2011-10-28 11:36         ` Anthony G. Basile
2011-10-28 17:20           ` Nirbheek Chauhan [this message]
2011-10-30 22:24         ` Petteri Räty
2011-10-31  1:04           ` Ryan Hill
2011-10-28  3:03       ` Nirbheek Chauhan

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=CADqQcK4x1C7CX5ZA5pO52XhOmYcrLoBZCCjNZTKLOV1siJJexQ@mail.gmail.com \
    --to=nirbheek@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