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: Hans de Graaff <graaff@g.o>
Subject: Re: Re: RFC: an eclass for github snapshots?
Date: Wed, 08 Jun 2011 17:43:38 +0200
On Wed, 2011-06-08 at 09:17 +0200, Ulrich Mueller wrote:

> The value of S that is assigned in global scope (i.e. the one
> containing the wildcard) violates it.

Ah, right, I initially read Donnie's quotation from PMS as an
endorsement for our approach, but that is only true for our EAPI=4
solution where we only change S within a function.

That leaves the question what to do with the approach for EAPI=2,3. I'd
rather not risk breaking ebuilds by removing this support just for a
violation of PMS if there is no real problem exposed by it.

Kind regards,

Hans
Attachment:
signature.asc (This is a digitally signed message part)
Replies:
Re: Re: RFC: an eclass for github snapshots?
-- Ciaran McCreesh
References:
RFC: an eclass for github snapshots?
-- Michał Górny
Re: RFC: an eclass for github snapshots?
-- Diego Elio Pettenò
Re: RFC: an eclass for github snapshots?
-- Ulrich Mueller
Re: Re: RFC: an eclass for github snapshots?
-- Donnie Berkholz
Re: Re: RFC: an eclass for github snapshots?
-- Ulrich Mueller
Re: Re: RFC: an eclass for github snapshots?
-- Hans de Graaff
Re: Re: RFC: an eclass for github snapshots?
-- Ulrich Mueller
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: RFC: an eclass for github snapshots?
Next by thread:
Re: Re: RFC: an eclass for github snapshots?
Previous by date:
Re: Gentoo package statistics -- GSoC 2011
Next by date:
Re: Gentoo package statistics -- GSoC 2011


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.