From: Mike Gilbert <floppym@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: Ian Stakenvicius <axs@gentoo.org>,
gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] Reducing exceptionality cases for PYTHON_SINGLE_TARGET
Date: Wed, 29 Oct 2014 16:21:20 -0400 [thread overview]
Message-ID: <CAJ0EP42ZiuDmRFBYj1u=B51pRdfour7AfPLQ4ZHA5Gm8sHYDDg@mail.gmail.com> (raw)
In-Reply-To: <20141029210925.3774b12f@pomiot.lan>
On Wed, Oct 29, 2014 at 4:09 PM, Michał Górny <mgorny@gentoo.org> wrote:
> Dnia 2014-10-29, o godz. 14:39:52
> Ian Stakenvicius <axs@gentoo.org> napisał(a):
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 29/10/14 02:31 PM, Michał Górny wrote:
>> >
>> > This is ugly.
>> >
>> > I was rather thinking of making all eclasses put +impl in IUSE when
>> > only one implementation is supported.
>> >
>>
>> ...how would that work? PYTHON_SINGLE_TARGET as set in make.conf
>> overrides the +impl in IUSE.
>
> Does it?
>
Yes, it does.
Personally, I would prefer to remove PYTHON_SINGLE_TARGET from
profiles and have all python-single-r1 ebuilds set a +impl in IUSE.
Just need a reasonable algorithm for determining what that impl should
be.
next prev parent reply other threads:[~2014-10-29 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 18:17 [gentoo-python] Reducing exceptionality cases for PYTHON_SINGLE_TARGET Ian Stakenvicius
2014-10-29 18:25 ` W. Trevor King
2014-10-29 18:40 ` Ian Stakenvicius
[not found] ` <5451330B.7000705@gentoo.org>
[not found] ` <20141029184254.GI15443@odin.tremily.us>
2014-10-29 18:47 ` Ian Stakenvicius
2014-10-29 18:31 ` Michał Górny
2014-10-29 18:39 ` Ian Stakenvicius
2014-10-29 20:09 ` Michał Górny
2014-10-29 20:21 ` Mike Gilbert [this message]
2014-10-29 20:25 ` Michał Górny
2014-10-30 19:21 ` Ian Stakenvicius
2014-10-30 19:43 ` Michał Górny
2014-10-30 20:26 ` Mike Gilbert
2014-10-30 21:31 ` Michał Górny
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='CAJ0EP42ZiuDmRFBYj1u=B51pRdfour7AfPLQ4ZHA5Gm8sHYDDg@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=axs@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