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 12:16:31 -0400 [thread overview]
Message-ID: <CAJ0EP42C2SCQ4sRLOPK9OorVNA_wWOZ28LPsvbinLN4T6VJ5wQ@mail.gmail.com> (raw)
In-Reply-To: <CAET+hMS0hLatwztXQTEVG=R2yjnn3DvEYnhohETZRf7Mtqjz9A@mail.gmail.com>
On Mon, Jul 30, 2012 at 12:05 PM, Matthew Summers
<quantumsummers@gentoo.org> wrote:
> Could we not just set a dep as =dev-lang/python:2 so that any version
> of python-2.* would satisfy the dep? Or, would this cause issues in
> avoiding old versions of python (python-2.5)? It might be enough to
> change the portage ebuild to work as it does now for the USE python2
> and python3, but in the case where those flags are not set, then just
> pull in python:2 which would yield the latest stable version of
> python-2.*
Using an || dep with to separate =dev-lang/python-2* and
=dev-lang/python-3* (or something roughly equivalent) is enough to
trigger the desired behavior from portage. See my previous message in
this thread.
> For python-updater, I might be inclined to add similar USE to portage
> to manage the deps.
No need for the use-flags. Again, I think the || dep is sufficient.
next prev parent reply other threads:[~2012-07-30 16:16 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
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 [this message]
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=CAJ0EP42C2SCQ4sRLOPK9OorVNA_wWOZ28LPsvbinLN4T6VJ5wQ@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