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-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ciaran McCreesh <ciaran.mccreesh@...>
Subject: Re: [RFC] obs eclasses
Date: Wed, 14 Sep 2011 06:37:09 +0100
On Tue, 13 Sep 2011 17:58:15 +0200
Patrick Lauer <patrick@g.o> wrote:
> > It's because people want to pretend that it's possible for
> > incredibly outdated systems (those with bash-3 only) to be updated.
> 
> Actually it's worse - PMS enforces this, and the only clean way out is
> to patch/fix/extend PMS to allow bash4 - but that breaks compatibility
> in silly ways.
> 
> The proper way to handle that? I'm not sure, since we had a long fight
> to get PMS to acknowledge bash 3.2 instead of 3.0 I'm mostly ignoring
> PMS as it doesn't care about reality.

The proper fix for this, along with a whole bunch of other things, is
GLEP 55. Don't blame the PMS team for that not having been implemented.

As for you ignoring the specification, the reason that problems like
this exist is precisely because of you doing that. Do you code websites
based purely upon what Internet Explorer supports?

-- 
Ciaran McCreesh
Attachment:
signature.asc (PGP signature)
References:
[RFC] obs eclasses
-- Michal Hrusecky
Re: [RFC] obs eclasses
-- Amadeusz Żołnowski
Re: [RFC] obs eclasses
-- Joshua Kinard
Re: [RFC] obs eclasses
-- Amadeusz Żołnowski
Re: [RFC] obs eclasses
-- Donnie Berkholz
Re: [RFC] obs eclasses
-- Patrick Lauer
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [RFC] obs eclasses
Next by thread:
Re: [RFC] obs eclasses
Previous by date:
Re: new `usex` helper
Next by date:
Re: [RFC] obs eclasses


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

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