From: "Michał Górny" <mgorny@gentoo.org>
To: Patrick McLean <chutzpah@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] How to migrate to the new scheme of Python scripts?
Date: Thu, 12 Sep 2013 19:49:52 +0200 [thread overview]
Message-ID: <20130912194952.36d0662f@gentoo.org> (raw)
In-Reply-To: <20130912102018.782a45e6@chiana.av1.gaikai.int>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Dnia 2013-09-12, o godz. 10:20:18
Patrick McLean <chutzpah@gentoo.org> napisał(a):
> You could make sure that python-exec:2 is marked ~arch and in the
> eclass check the version installed and switch according to that. For
> stable users everything will stay the same, and for ~arch users all new
> installs/upgrades will be switched to the new system. This will even
> work if we want to mask it for a bit, so developers can test before
> letting it into ~arch.
Well, as I said on IRC, that sounds like a wonderful idea, thanks.
Just that most of it will require EAPI 5 for := dep on python-exec. For
EAPI 4 packages (namely: snakeoil), we can just use python-exec:0 for
now and switch at a later time.
Remaining case is how to handle the packages which rely on specific
kind of wrapping. I guess we can make them explicitly pull in
python-exec:0, plus add some switch to control the used version
or use EAPI=4 for them.
I will try to implement that on yet another branch of my
gx86-working-tree.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-09-12 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 8:49 [gentoo-python] How to migrate to the new scheme of Python scripts? Michał Górny
2013-09-12 17:20 ` Patrick McLean
2013-09-12 17:49 ` Michał Górny [this message]
2013-09-12 19:27 ` 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=20130912194952.36d0662f@gentoo.org \
--to=mgorny@gentoo.org \
--cc=chutzpah@gentoo.org \
--cc=gentoo-python@lists.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