From: "Jeremy Olexa" <darkside@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] bash version in ebuilds/eclasses...non-compliance and what to do?
Date: Tue, 16 Dec 2008 17:46:44 -0600 [thread overview]
Message-ID: <90b936c0812161546u7df31557t603f6d78c71016bd@mail.gmail.com> (raw)
Exhibit A:
http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/python.eclass?r1=1.48&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.
-Jeremy
[0]: See bash CHANGES file. "+=" is new to bash-3.1
[1]: "The ebuild file format is in its basic form a subset of the
format of a bash script. The interpreter is assumed to be GNU bash,
version 3.0 or later." -Chapter 6 "Ebuild File Format" [2]
[2]: http://dev.gentoo.org/~ferdy/pms/pms-eapi-2-approved-2008-09-25.pdf
next reply other threads:[~2008-12-16 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 23:46 Jeremy Olexa [this message]
2008-12-20 5:35 ` [gentoo-dev] Re: bash version in ebuilds/eclasses...non-compliance and what to do? 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 ` [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=90b936c0812161546u7df31557t603f6d78c71016bd@mail.gmail.com \
--to=darkside@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