From: "Michał Górny" <mgorny@gentoo.org>
To: Dirkjan Ochtman <djc@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org, hasufell@gentoo.org
Subject: Re: [gentoo-python] Re: USE flag dependencies on Python implementation
Date: Wed, 26 Sep 2012 08:46:22 +0200 [thread overview]
Message-ID: <20120926084622.46befd11@pomiocik.lan> (raw)
In-Reply-To: <CAKmKYaDVEZcC08f1Fk5+-ThHwoS-fWkvuuhyv4KGji81jFN1UA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Wed, 26 Sep 2012 08:42:21 +0200
Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Tue, Sep 25, 2012 at 11:59 PM, Michał Górny <mgorny@gentoo.org> wrote:
> > What are your opinions, ideas?
>
> Let's not solve it in the eclass, let's solve it in the implementation ebuilds.
>
> I.e. cpython, pypy, jython gets all the same flags. If an
> implementation unconditionally includes something that's not selected
> (i.e. the system has -threads for PyPy), it gets ignored. If a flag is
> required that the implementation doesn't support, the ebuild dies at
> some early stage (somewhat similar to check-reqs like things).
>
> I think you're massively overthinking this stuff.
But then you're introducing a bunch of flags which do nothing. However,
if you mask them in the base profile, this may actually get acceptable.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-09-26 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 21:59 [gentoo-python] USE flag dependencies on Python implementation Michał Górny
2012-09-26 6:42 ` [gentoo-python] " Dirkjan Ochtman
2012-09-26 6:46 ` Michał Górny [this message]
2012-09-26 6:48 ` Dirkjan Ochtman
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=20120926084622.46befd11@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=djc@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=hasufell@gentoo.org \
--cc=python@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