From: David Leverton <levertond@googlemail.com>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Bash features
Date: Sat, 9 Jan 2010 20:50:17 +0000 [thread overview]
Message-ID: <201001092050.17773.levertond@googlemail.com> (raw)
In-Reply-To: <19272.52850.175719.236536@a1i15.kph.uni-mainz.de>
On Saturday 09 January 2010 18:44:02 Ulrich Mueller wrote:
> > 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".
>
> Then we could simply have said "must be parsable with =bash-3.2" which
> we didn't. Clearly, the main idea was to disallow usage of bash-4*
> features.
That would completely defeat the purpose of specifying a version at all.
The most sensible interpretation would be to treat the bash version
requirement in the same way as an ebuild dependency. If an ebuild says
>=app-shells/bash-3.2 (it should be >= here, not =*, because ebuilds need to
work with bash 4 too, but the principle is the same), then it means the
ebuild is expected to work with /any/ version that matches the dependency.
The only difference is that we have a spec that defines the "dependency"
which ebuilds are supposed to respect, as opposed to documenting the
requirements of a package that someone already wrote.
next prev parent reply other threads:[~2010-01-09 22:06 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
2010-01-09 18:44 ` Ulrich Mueller
2010-01-09 20:22 ` Christian Faulhammer
2010-01-09 20:50 ` David Leverton [this message]
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=201001092050.17773.levertond@googlemail.com \
--to=levertond@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