From: Dirkjan Ochtman <djc@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>,
Gentoo Python Project <python@gentoo.org>
Subject: [gentoo-python] Re: Package supporting single implementation only -- auxiliary variable solution
Date: Mon, 19 Nov 2012 10:57:52 +0100 [thread overview]
Message-ID: <CAKmKYaD-NXbeR4UGD4HyNF_tR+1HUOuB-_M-f8eA5rd_3KiMpg@mail.gmail.com> (raw)
In-Reply-To: <20121115224425.5762484c@pomiocik.lan>
On Thu, Nov 15, 2012 at 10:44 PM, Michał Górny <mgorny@gentoo.org> wrote:
> Of course, a MIP would not be allowed to depend on a SIP.
How big of a problem would this be?
> To sum it up quickly, the aux variable solution:
>
> Advantages:
> - painless for most of our users,
> - explicit, transparent,
> - simple and matching SIP->SIP and SIP->MIP deps.
>
> Disadvantages:
> - a bit redundant,
Given the requirement for enabling multiple implementation in
PYTHON_TARGETS, which I feel strongly about, there has to be a choice
which one of the implementations will be target for SINGLE_TARGET
packages. Adding a variable for that, therefore, doesn't seem
redundant.
> - does not solve the issue for py3-only SIP packages,
I guess this might become a problem in the future. Once we have both
py2-only SIP packages and py3-only SIP packages, we have a bit of a
problem. Maybe we should think more about that.
> - may require explicit action when changing PYTHON_TARGETS.
Yeah, I don't see a problem with this. In particular, it seems
unlikely that many people will setup their system to exclude the
default SINGLE_TARGET impl (2.7) from their TARGETS.
Cheers,
Dirkjan
next prev parent reply other threads:[~2012-11-19 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 21:44 [gentoo-python] Package supporting single implementation only -- auxiliary variable solution Michał Górny
2012-11-19 9:57 ` Dirkjan Ochtman [this message]
2012-11-19 10:17 ` [gentoo-python] " 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=CAKmKYaD-NXbeR4UGD4HyNF_tR+1HUOuB-_M-f8eA5rd_3KiMpg@mail.gmail.com \
--to=djc@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@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