From: Christian Faulhammer <fauli@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Bash features
Date: Sun, 10 Jan 2010 16:09:21 +0100 [thread overview]
Message-ID: <20100110160921.1ce7e907@gentoo.org> (raw)
In-Reply-To: <201001092050.17773.levertond@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Hi,
David Leverton <levertond@googlemail.com>:
> 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.
We can leave the spec as it is, in the end it was a bug fix which
resulted in the behaviour we wanted to specify.
V-Li
--
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 --]
next prev parent reply other threads:[~2010-01-10 16:03 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
2010-01-10 15:09 ` Christian Faulhammer [this message]
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=20100110160921.1ce7e907@gentoo.org \
--to=fauli@gentoo.org \
--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