From: Christian Faulhammer <fauli@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Bash features
Date: Sat, 9 Jan 2010 16:00:23 +0100 [thread overview]
Message-ID: <20100109160023.5dcdef17@gentoo.org> (raw)
In-Reply-To: <20100109085821.7cf45202@snowmobile>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Hi,
Ciaran McCreesh <ciaran.mccreesh@googlemail.com>:
> On Sat, 9 Jan 2010 09:18:19 +0100
> Ulrich Mueller <ulm@gentoo.org> wrote:
> > > Didn't the Council say that if it ever happened again, there
> > > should be forced reverts rather than updating PMS retroactively?
> >
> > Yes, but any =bash-3.2* is still allowed:
> >
> > | Vote (6 yes, 1 no): Ebuilds must be completely parsable with
> > | =bash-3.2*, any use of later bash features will be reverted.
>
> Doesn't the way that's worded mean "it has to work with every single
> 3.2 patch", though? I take that to mean "must be completely parsable
> with bash-3.2_p0 through bash-3.2_p9999", not "must work with at least
> one version of bash-3.2_psomething".
So one has to work around obvious bugs to satisfy p0? p9999 will
support everything p0 has while eliminating bugs that cripple official
features advertised for p0.
V-Li
--
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
<URL:http://gentoo.faulhammer.org/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-09 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 23:42 [gentoo-pms] Bash features Christian Faulhammer
2010-01-09 0:08 ` Ciaran McCreesh
2010-01-09 8:18 ` Ulrich Mueller
2010-01-09 8:58 ` Ciaran McCreesh
2010-01-09 14:17 ` Petteri Räty
2010-01-09 15:00 ` Christian Faulhammer [this message]
2010-01-09 18:44 ` Ulrich Mueller
2010-01-09 20:22 ` Christian Faulhammer
2010-01-09 20:50 ` David Leverton
2010-01-10 15:09 ` Christian Faulhammer
2010-01-09 14:58 ` Christian Faulhammer
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=20100109160023.5dcdef17@gentoo.org \
--to=fauli@gentoo.org \
--cc=gentoo-pms@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