Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-pms
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-pms@g.o
From: David Leverton <levertond@...>
Subject: Re: Bash features
Date: Sat, 9 Jan 2010 20:50:17 +0000
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.

Re: Bash features
-- Christian Faulhammer
Bash features
-- Christian Faulhammer
Re: Bash features
-- Ciaran McCreesh
Re: Bash features
-- Ulrich Mueller
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Bash features
Next by thread:
Re: Bash features
Previous by date:
Re: Bash features
Next by date:
Re: Bash features

Updated Jul 18, 2012

Summary: Archive of the gentoo-pms mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.