From: Alex Alexander <wired@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] openrc portage news item
Date: Fri, 29 Apr 2011 20:58:31 +0300 [thread overview]
Message-ID: <20110429175831.GB11073@lust> (raw)
In-Reply-To: <BANLkTimWB9MU=UP1+1QnQSFSKtbt2MyTGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Fri, Apr 29, 2011 at 01:52:15PM -0400, Rich Freeman wrote:
> On Fri, Apr 29, 2011 at 1:25 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>>> On Fri, 29 Apr 2011, Alex Alexander wrote:
> >
> >> please have a look at the attached patch.
> >
> >> -EAPI="1"
> >> +EAPI="4"
> >
> > Shouldn't the ebuild's phase functions be updated from "EAPI 0 style"
> > to "EAPI 2 style" too?
>
> If the goal is to get this stable in a week, and bypass the 1 month
> waiting period, do we really want to change EAPI at this point? From
> an end-user perspective updating the EAPI on the ebuild provides no
> benefit. Why not just deal with that in a future revision?
>
> I don't see much value in rewriting the ebuild to use a new EAPI
> simply because 4 > 1.
EAPI was bumped so I could use pkg_pretend, please check out my
(incomplete) patch.
--
Alex Alexander | wired
+ Gentoo Linux Developer
++ www.linuxized.com
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-04-29 17:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 18:15 [gentoo-dev] openrc portage news item William Hubbs
2011-04-13 18:27 ` Thomas Beierlein
2011-04-13 18:32 ` justin
2011-04-13 18:41 ` "Paweł Hajdan, Jr."
2011-04-13 19:58 ` William Hubbs
2011-04-14 8:09 ` [gentoo-dev] " Duncan
2011-04-14 11:44 ` Rich Freeman
2011-04-15 14:04 ` Peter Hjalmarsson
2011-04-15 19:01 ` Duncan
2011-04-13 19:56 ` [gentoo-dev] " William Hubbs
2011-04-14 5:30 ` justin
2011-04-14 7:21 ` Dirkjan Ochtman
2011-04-14 8:19 ` justin
2011-04-14 8:40 ` [gentoo-dev] " Duncan
2011-04-14 14:44 ` Dale
2011-04-14 15:41 ` Matthew Summers
2011-04-14 16:12 ` Dale
2011-04-14 18:48 ` William Hubbs
2011-04-14 10:32 ` [gentoo-dev] " Kfir Lavi
2011-04-14 10:32 ` Kfir Lavi
2011-04-14 10:51 ` Tomá? Chvátal
2011-04-14 11:03 ` Pacho Ramos
2011-04-14 11:21 ` Thomas Beierlein
2011-04-14 11:27 ` Sylvain Alain
2011-04-21 1:12 ` Donnie Berkholz
2011-04-21 2:23 ` Jeroen Roovers
2011-04-21 2:34 ` Jeroen Roovers
2011-04-22 10:39 ` Lars Wendler
2011-04-29 18:41 ` Brian Harring
2011-04-30 2:19 ` William Hubbs
2011-04-30 4:59 ` Brian Harring
2011-04-30 7:13 ` [gentoo-dev] " Duncan
2011-04-30 11:46 ` Brian Harring
2011-04-30 12:03 ` Rich Freeman
2011-04-30 12:58 ` Brian Harring
2011-04-30 13:06 ` Jeremy Olexa
2011-04-30 13:40 ` Brian Harring
2011-04-29 7:08 ` [gentoo-dev] " William Hubbs
2011-04-29 11:21 ` Rich Freeman
2011-04-29 11:28 ` Ciaran McCreesh
2011-04-29 17:18 ` Alex Alexander
2011-04-29 17:25 ` Ulrich Mueller
2011-04-29 17:32 ` Alex Alexander
2011-04-29 17:52 ` Rich Freeman
2011-04-29 17:58 ` Alex Alexander [this message]
2011-04-30 0:34 ` William Hubbs
2011-04-30 9:04 ` Sergei Trofimovich
2011-04-30 12:41 ` Roy Bamford
2011-04-29 14:27 ` [gentoo-dev] " Duncan
2011-05-01 19:12 ` [gentoo-dev] " William Hubbs
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=20110429175831.GB11073@lust \
--to=wired@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