public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick McLean <chutzpah@gentoo.org>
To: Mike Gilbert <floppym@gentoo.org>
Cc: "Michał Górny" <mgorny@gentoo.org>,
	gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] [PATCH] python.eclass: Add 3.4 to _CPYTHON3_GLOBALLY_SUPPORTED_ABIS
Date: Tue, 18 Feb 2014 21:19:03 -0800	[thread overview]
Message-ID: <20140218211903.26de32ab@moya.linuxfreak.ca> (raw)
In-Reply-To: <CAJ0EP430HQAffbkZ1qR+CBbf8WCUJD463-dDb49NOnCYm_+NRw@mail.gmail.com>

On Mon, 17 Feb 2014 14:15:41 -0500
Mike Gilbert <floppym@gentoo.org> wrote:

> On Mon, Feb 17, 2014 at 2:12 PM, Michał Górny <mgorny@gentoo.org>
> wrote:
> > Dnia 2014-02-17, o godz. 13:44:04
> > Mike Gilbert <floppym@gentoo.org> napisał(a):
> >
> > To be honest, I'm against adding new implementations to the old
> > eclass. I'm all for letting it rot and not adding extra work on
> > maintaining ebuilds using it. Since it is opt-out, adding the new
> > implementation would mean we need to add restrictions to ebuilds.
> >
> > Instead, I'd just say that we require the new eclass for py3.4.
> 
> That's fine by me, as long as it doesn't break anything. I can't think
> of any such breakage off the top of my head.
> 
Agreed, I don't see how it could break anything and it could help
speed up migrating the remaining packages to the new eclasses.


      reply	other threads:[~2014-02-19  5:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 18:44 [gentoo-python] [PATCH] python.eclass: Add 3.4 to _CPYTHON3_GLOBALLY_SUPPORTED_ABIS Mike Gilbert
2014-02-17 19:12 ` Michał Górny
2014-02-17 19:15   ` Mike Gilbert
2014-02-19  5:19     ` Patrick McLean [this message]

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=20140218211903.26de32ab@moya.linuxfreak.ca \
    --to=chutzpah@gentoo.org \
    --cc=floppym@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=mgorny@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