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 change: Call ebuild functions from trusted working directory
Date: Mon, 13 Oct 2008 19:28:53 +0100	[thread overview]
Message-ID: <20081013192853.4454d779@snowmobile> (raw)
In-Reply-To: <20081013174221.GB23706@comet>

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

On Mon, 13 Oct 2008 10:42:21 -0700
Donnie Berkholz <dberkholz@gentoo.org> wrote:
> It seems to me that this is an EAPI=0 change. Since EAPI=1 and EAPI=2 
> are just differences to EAPI=0, they wouldn't be voted on. Since
> EAPI=0 isn't actually approved yet, council wouldn't vote either. As
> it's a draft standard, this would be resolved amongst package-manager 
> developers and PMS editors.

It's a retroactive change to EAPI 0 that requires changes from package
managers and has security implications... Robert isn't requesting that
we specify and mandate existing behaviour here, so it's not really
something that should be left up to PMS to decide and enforce.

I mean, if the Council's comfortable with PMS being used to force
package manager changes for things that aren't obviously bugs, we could
do it without asking, but that looks a lot like a slippery slope...

-- 
Ciaran McCreesh

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

  parent reply	other threads:[~2008-10-13 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 19:03 [gentoo-dev] EAPI change: Call ebuild functions from trusted working directory Robert Buchholz
2008-10-13 17:42 ` Donnie Berkholz
2008-10-13 18:20   ` Wulf C. Krueger
2008-10-13 18:56     ` Donnie Berkholz
2008-10-13 18:28   ` Ciaran McCreesh [this message]
2008-10-17  0:41     ` Robert Buchholz
2008-10-24 11:36       ` Robert Buchholz

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=20081013192853.4454d779@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