From: Ulrich Mueller <ulm@gentoo.org>
To: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Bash features
Date: Sat, 9 Jan 2010 09:18:19 +0100 [thread overview]
Message-ID: <19272.15307.279638.864461@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20100109000834.6f6ed79a@snowmobile>
>>>>> On Sat, 9 Jan 2010, Ciaran McCreesh wrote:
> On Sat, 9 Jan 2010 00:42:01 +0100
> Christian Faulhammer <fauli@gentoo.org> wrote:
>> as I now learnt, Bash 3.2 vanilla is not enough for some eclasses
>> to run. Patchlevel 48 is needed.
What eclasses are this? _p48 isn't marked as stable.
>> Should we tighten the version string for Bash?
I don't think there's a need for this, as the patches are only
bugfixes.
> 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.
See also the log [1] where the example of 3.2_p39 is explicitly
mentioned at one point.
Ulrich
[1] <http://www.gentoo.org/proj/en/council/meeting-logs/20091109.txt>
next prev parent reply other threads:[~2010-01-09 10:05 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 [this message]
2010-01-09 8:58 ` Ciaran McCreesh
2010-01-09 14:17 ` Petteri Räty
2010-01-09 15:00 ` Christian Faulhammer
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=19272.15307.279638.864461@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=ciaran.mccreesh@googlemail.com \
--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