From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] Python 3 in Gentoo
Date: Mon, 30 Jul 2012 11:19:06 -0400 [thread overview]
Message-ID: <CAJ0EP41WDQDFe6ekHj_EP5OyTT2Z_--Df+JeEaX_j=bG+KLfig@mail.gmail.com> (raw)
In-Reply-To: <CAKmKYaC56sO-6LJSegHvqW-adU9WHvWQb4AScaErm+YadAky4w@mail.gmail.com>
On Mon, Jul 30, 2012 at 3:36 AM, Dirkjan Ochtman <djc@gentoo.org> wrote:
> I agree that installing both is probably overkill for most users. I
> think the solution is somewhere outside the dev-lang/python package,
> though, in having the system set or portage or whatever the hell it is
> that first pulls in python prefer python-2.
I looked into this, and there are currently two things that will pull
python-3 into a stage3:
1. sys-apps/portage due to its >=dev-lang/python-2.7[ssl] dependency.
2. app-admin/python-updater has a bare "dev-lang/python" dependency.
I have verified that if you install python:2.7, and adjust those
dependencies to the following, portage will no longer try to pull in
python-3.2 on a world update.
sys-apps/portage:
DEPEND="|| ( =dev-lang/python-3*[ssl] dev-lang/python:2.7[ssl]
dev-lang/python:2.6[threads,ssl] )"
app-admin/python-updater:
DEPEND="|| ( dev-lang/python-3* dev-lang/python-2* )"
The || deps are key here; this causes portage to weight an already
installed package over the rest.
In fact, if you reverse the order of python-3 and python-2, that
SHOULD cause python-2 to be pulled into the stage building process
instead of python-3.
So, another possible alternative here is to scour the tree, replacing
any dependencies on dev-lang/python with || deps. I believe
python.eclass would also need to be updated. Does that sound like an
acceptable solution?
next prev parent reply other threads:[~2012-07-30 15:19 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 2:13 [gentoo-python] Python 3 in Gentoo Mike Gilbert
2012-07-30 2:23 ` Richard Yao
2012-07-30 5:38 ` Rafael Goncalves Martins
2012-07-30 7:36 ` Dirkjan Ochtman
2012-07-30 8:23 ` Richard Yao
2012-07-30 8:32 ` Dirkjan Ochtman
2012-07-30 9:06 ` Michał Górny
2012-07-30 9:09 ` Dirkjan Ochtman
2012-07-30 9:16 ` Michał Górny
2012-07-30 9:23 ` Dirkjan Ochtman
2012-07-30 9:50 ` Michał Górny
2012-07-30 11:56 ` Dirkjan Ochtman
2012-07-30 13:11 ` Matthew Summers
2012-07-30 13:18 ` Matthew Summers
2012-07-30 13:39 ` Nikolaj Sjujskij
2012-07-30 14:05 ` Jesus Rivero (Neurogeek)
2012-07-31 7:11 ` Nikolaj Sjujskij
2012-07-31 12:09 ` Ben de Groot
2012-07-31 12:14 ` Nikolaj Sjujskij
2012-07-31 14:40 ` Ben de Groot
2012-07-31 16:46 ` Nikolaj Sjujskij
2012-07-30 14:00 ` Jesus Rivero (Neurogeek)
2012-07-30 14:04 ` Michał Górny
2012-07-30 14:07 ` Matthew Summers
2012-07-30 14:11 ` Michał Górny
2012-07-30 15:19 ` Mike Gilbert [this message]
2012-07-30 15:22 ` Dirkjan Ochtman
2012-07-30 15:30 ` Mike Gilbert
2012-07-30 15:40 ` Dirkjan Ochtman
2012-07-30 15:56 ` Mike Gilbert
2012-07-30 16:05 ` Matthew Summers
2012-07-30 16:16 ` Mike Gilbert
2012-07-30 16:20 ` Matthew Summers
2012-07-30 16:53 ` Dirkjan Ochtman
2012-07-30 17:05 ` Mike Gilbert
2012-07-31 15:31 ` Mike Gilbert
2012-08-08 21:07 ` Mike Gilbert
2012-08-08 21:44 ` Thomas Sachau
2012-08-08 22:09 ` Jesus Rivero (Neurogeek)
2012-08-13 19:05 ` Richard Yao
2012-08-13 9:46 ` Dirkjan Ochtman
2012-08-13 19:07 ` Richard Yao
2012-08-13 19:38 ` Dirkjan Ochtman
2012-08-31 2:13 ` Mike Gilbert
2012-09-02 12:21 ` Thomas Sachau
2012-09-02 17:16 ` Mike Gilbert
2012-09-02 17:34 ` Michał Górny
2012-09-02 17:54 ` Mike Gilbert
2012-09-02 19:02 ` Michał Górny
2012-09-03 21:12 ` Mike Gilbert
2012-09-03 21:20 ` Michał Górny
2012-07-30 21:33 ` Thomas Sachau
2012-07-30 7:45 ` 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='CAJ0EP41WDQDFe6ekHj_EP5OyTT2Z_--Df+JeEaX_j=bG+KLfig@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-python@lists.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