public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI 2 is brokened :(
Date: Fri, 10 Oct 2008 14:56:19 +0100	[thread overview]
Message-ID: <20081010145619.2fb3381f@snowmobile> (raw)
In-Reply-To: <1223620364.5442.3.camel@localhost>

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

On Fri, 10 Oct 2008 09:32:44 +0300
Mart Raudsepp <leio@gentoo.org> wrote:
> > Of those, and those in overlays, and those that are going to be
> > committed over the next few weeks, how many use src_prepare to apply
> > security related patches?
> 
> A round zero. Security patches are going stable soon after entering
> portage tree, and EAPI=2 ebuilds can not go stable yet, as there is no
> package manager supporting EAPI=2 that is going to be stable in the
> next week or two (so maintainers make sure they don't use EAPI=2 for
> security fix revisions).

Oh really? So you're absolutely certain there aren't and won't soon be
any EAPI 2 bumps of non-EAPI 2 versions that include security patches?
And you're absolutely certain that there aren't, say, any packages that
sed a broken chmod in a makefile in src_prepare?

> I can not understand why this is dragged on. It was a bug, it is
> fixed. The sky is not falling and EAPI-2 is not broken - there was a
> bug in the implementation that is fixed.

The point of EAPI is to avoid these kinds of problems. The process is
failing and the fallout needs to be handled.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-10-10 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 18:53 [gentoo-dev] EAPI 2 is brokened :( Ciaran McCreesh
2008-10-09 21:47 ` Doug Goldstein
2008-10-09 21:53   ` Ciaran McCreesh
2008-10-09 22:22     ` Brian Harring
2008-10-09 22:34       ` Ciaran McCreesh
2008-10-09 23:38         ` Brian Harring
2008-10-09 23:55           ` Ciaran McCreesh
2008-10-10  6:32             ` Mart Raudsepp
2008-10-10 13:56               ` Ciaran McCreesh [this message]
2008-10-10 17:03                 ` Robert Buchholz
2008-10-10  7:05         ` Alec Warner
2008-10-09 22:19 ` 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=20081010145619.2fb3381f@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --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