From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bash version in ebuilds/eclasses...non-compliance and what to do?
Date: Fri, 15 Jan 2010 00:34:08 -0500 [thread overview]
Message-ID: <201001150034.08646.vapier@gentoo.org> (raw)
In-Reply-To: <90b936c0812161546u7df31557t603f6d78c71016bd@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1022 bytes --]
On Tuesday 16 December 2008 18:46:44 Jeremy Olexa wrote:
> Exhibit A:
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/python.eclass?r1=1.4
> 8&r2=1.49
>
> This causes me pain on my hosts that don't have >=bash-3.1[0] for
> /bin/bash. Because I can't install portage with an old bash until I
> get a new python installed which uses python.eclass which isn't
> supported with my /bin/bash (quite circular indeed)
>
> Technically there are workarounds for me...but it is still annoying.
> So...what do we do? A) Specifically allow >=bash-3.1 features in
> ebuilds/eclasses. or B) revert the commit because the PMS says[1] that
> we comply with >bash-3.0
>
> Please discuss, thanks.
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+ ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-01-15 5:34 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 ` Mike Frysinger [this message]
2010-01-15 10:46 ` [gentoo-dev] " Fabian Groffen
2010-01-15 15:13 ` [gentoo-dev] " 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=201001150034.08646.vapier@gentoo.org \
--to=vapier@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