public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: an eclass for github snapshots?
Date: Wed, 08 Jun 2011 17:43:38 +0200	[thread overview]
Message-ID: <1307547818.15732.4.camel@graaff.xs4all.nl> (raw)
In-Reply-To: <19951.8704.849945.147852@a1i15.kph.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

  reply	other threads:[~2011-06-08 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  6:27 [gentoo-dev] RFC: an eclass for github snapshots? Michał Górny
2011-05-30  9:35 ` [gentoo-dev] " Diego Elio Pettenò
2011-05-30 11:21   ` Ulrich Mueller
2011-05-30 11:44     ` Diego Elio Pettenò
2011-06-07 14:17     ` Donnie Berkholz
2011-06-07 18:16       ` Ulrich Mueller
2011-06-08  6:01         ` Hans de Graaff
2011-06-08  7:17           ` Ulrich Mueller
2011-06-08 15:43             ` Hans de Graaff [this message]
2011-06-08 15:50               ` Ciaran McCreesh
2011-06-08 19:20                 ` Hans de Graaff

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=1307547818.15732.4.camel@graaff.xs4all.nl \
    --to=graaff@gentoo.org \
    --cc=gentoo-dev@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