From: Christian Faulhammer <fauli@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: bash version in ebuilds/eclasses...non-compliance and what to do?
Date: Fri, 15 Jan 2010 16:13:22 +0100 [thread overview]
Message-ID: <20100115161322.164b1ede@gentoo.org> (raw)
In-Reply-To: <201001150034.08646.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
Hi,
Mike Frysinger <vapier@gentoo.org>:
> btw, latest python.eclass requires bash-3.2+ due to parsing errors in
> the regex checks:
> $ bash-3.1 -c '[[ a =~ ^(a|b)$ ]]'
> bash-3.1: -c: line 0: syntax error in conditional expression:
> unexpected token `(' bash-3.1: -c: line 0: syntax error near `^(a'
>
> we could quote these or require bash-3.2+ ...
We discussed it briefly on the -pms mailing list [1].
V-Li
[1]http://archives.gentoo.org/gentoo-pms/msg_f4fee4c3a79ae4f37eaf4c4ebce6aafe.xml
--
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 --]
prev parent reply other threads:[~2010-01-15 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 23:46 [gentoo-dev] bash version in ebuilds/eclasses...non-compliance and what to do? Jeremy Olexa
2008-12-20 5:35 ` [gentoo-dev] " Steve Long
2008-12-20 9:42 ` Fabian Groffen
2008-12-24 11:31 ` [gentoo-dev] " Steve Long
2008-12-20 13:54 ` [gentoo-dev] " Ciaran McCreesh
2010-01-15 5:34 ` [gentoo-dev] " Mike Frysinger
2010-01-15 10:46 ` Fabian Groffen
2010-01-15 15:13 ` Christian Faulhammer [this message]
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=20100115161322.164b1ede@gentoo.org \
--to=fauli@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