List Archive: gentoo-council
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Thu, 12 Feb 2009 09:10:55 -0800
Donnie Berkholz <email@example.com> wrote:
> On 16:21 Thu 12 Feb , Ciaran McCreesh wrote:
> > On Thu, 12 Feb 2009 08:16:45 -0800
> > Donnie Berkholz <firstname.lastname@example.org> wrote:
> > > I think we should update the PMS to bash 3.1 to allow for '+='
> > > use. I looked through the bash changelog, and 3.2 didn't appear
> > > to add any new and useful features. We should then require a new
> > > EAPI for new bash features.
> > That would require GLEP 55 to provide any protection. A new EAPI on
> > its own wouldn't be enough.
> What kind of protection are you talking about
The problem is, without GLEP 55, EAPI isn't known before the ebuild is
sourced to generate metadata. If someone uses += anywhere that older
bash looks when sourcing for metadata generation (which is not just
global scope), the package manager won't know that the EAPI says that
bash-3.1 is required for sourcing until after it's already done the
sourcing, by which point it's too late.
> and is it already in place for every bash feature in 3.0?
The bash 3.0 transition was done before EAPIs came along, and was
handled by the old fashioned "wait for ages until we're absolutely sure
that everyone has bash 3.0 before continuing" method.