public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hasufell@gentoo.org
Subject: Re: [gentoo-dev] [RFC] Cleaning up PMS to have ${D} not end with a slash
Date: Sun, 14 Apr 2013 17:01:52 +0200	[thread overview]
Message-ID: <20130414170152.09f8984f@pomiocik.lan> (raw)
In-Reply-To: <516AB9E1.1040504@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sun, 14 Apr 2013 16:14:57 +0200
hasufell <hasufell@gentoo.org> wrote:

> On 04/13/2013 11:23 PM, Michał Górny wrote:
> > Your thoughts?
> > 
> 
> Sounds ok, but how will the transition happen exactly? Will the
> behavior just change for new EAPIs or for all? If for all, who will do
> the tinderbox run?

I am fine with whatever suits people.

New EAPI would be simpler for ebuilds but harder for eclasses (which
will have to support both cases). Additionally, there will be
the increased risk that thoughtless EAPI switch will silently trigger
failure.

Retroactive change has the benefit that most of the current uses become
valid and all ebuilds start to work correctly the moment we finish it.
Noticeably, the transition will occur with a portage upgrade so any
testing can be done through p.masking a single package.

That said, the tinderbox run would probably end up being community
effort in an --emptytree @world update.

- -- 
Best regards,
Michał Górny
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQJ8BAEBCgBmBQJRasTgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1RUJGMjBGOTk2RkIzQzIyQ0M2RkNBNDBC
QUJGMUQ1RkY4QzgxMTBBAAoJELq/HV/4yBEK0XkQAJkvkv86axzdMJyr7YtUm7w/
ESqLlS5mhqw66Q8Su6n1Rj8d0cfSd8KD9gbu0GdXOyrJ54HpxD5GrAByEjoE+guc
3/cBb1WIYCq30XZbGkBv2uJL92ysKukSaqbfTd+KimFvzc3okd7W0R+5Matiq6BZ
KktZZ+vMPXmVmbdnm7zoHqvvEB2rsQy/xwpNj3hXNheLdtvZ1oahAQoiCRi743tD
wViY+sCsnn4plsWOLpTibWpOwQD2Qn8sLoaC/exvVNsT7EkEX6REpkw0/V3uz566
jIXv92lcKpTGJdROBAMfhJ5dp8fsQlhJExzlIXPIuxkn4fs4dgKzlHNJ3M78xxGj
3Tt/QeAptEiCWWPMbxZW3yDGiMcGIo2faR2gPOotplBuq7F9KdSedYCw//WXfD9V
c5MjslDZCezFLYBhCK7JBILXsavSoAhkRXgjVREcquJeGUaZpkguSGDripZgFwWy
9N4buJ5WOscHT8foVgMNm9SxC565SgmbU6BKboSK1nJMNTwvaaLaJTIfuQvldbVF
HLMDYh13N66XJLZfLyy8jnR6HaYfSNTTUndu+n0a+nFkFA4vGYh9B135ikiR4d+N
DxO9KUnjuqTYiup8PAUsdfek62OJuFBMkN9biZlIy5ZahEixOPRQNquX36xze68b
z1EmfdaF7bjB7H7tHy1p
=CftZ
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-04-14 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 21:23 [gentoo-dev] [RFC] Cleaning up PMS to have ${D} not end with a slash Michał Górny
2013-04-14  8:31 ` Gregory M. Turner
2013-04-14 10:24 ` Peter Stuge
2013-04-14 11:32 ` Michał Górny
2013-04-14 11:34   ` Michał Górny
2013-04-14 14:14 ` hasufell
2013-04-14 15:01   ` Michał Górny [this message]
2013-04-14 14:22 ` Ciaran McCreesh
2013-04-14 14:58   ` Michał Górny
2013-04-14 16:39     ` Ciaran McCreesh
2013-04-14 16:59       ` Michał Górny
2013-04-15 10:56         ` Aaron W. Swenson
2013-04-15 11:01           ` Ciaran McCreesh
2013-04-15 17:31             ` [gentoo-dev] " Steven J. Long
2013-04-15 18:54               ` Gregory M. Turner
2013-04-18 23:02                 ` [gentoo-dev] " Steven J. Long

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=20130414170152.09f8984f@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hasufell@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