From: "Michał Górny" <mgorny@gentoo.org>
To: Dirkjan Ochtman <djc@gentoo.org>
Cc: Richard Yao <ryao@gentoo.org>, gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Python 3 in Gentoo
Date: Mon, 30 Jul 2012 11:50:32 +0200 [thread overview]
Message-ID: <20120730115032.105ccb91@pomiocik.lan> (raw)
In-Reply-To: <CAKmKYaB_X52taTGwjgFbJYDPRXcjOXM1n3E+_EkpNFC=bryOtw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Mon, 30 Jul 2012 11:23:31 +0200
Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Mon, Jul 30, 2012 at 11:16 AM, Michał Górny <mgorny@gentoo.org>
> wrote:
> > You're saying 'we should explore the option not to upgrade packages
> > without user explicitly saying "please upgrade this package"'.
>
> Yes, or until the package maintainer removes the annotation again.
>
> >> > Or maybe we should explore the option of fixing python.eclass to
> >> > not depend on random python versions implicitly?
> >>
> >> I don't know that it does, but I hope you can enlighten me!
> >
> > It does depend on python versions based on $USE_PYTHON. And
> > USE_PYTHON defaults to 2+3 if installed. If it pulls in Python 3,
> > it will pull in all the time unless you set USE_PYTHON manually and
> > remerge all the packages manually.
>
> It seems to me that we could fix USE_PYTHON to always depend only on 2
> unless it's explicitly set by the user, but it seems to me that
> Portage would, in that case, still pull python3 into the stages.
Portage will pull python3 if and only if anything depends on python:3.*
or anything depends on python without a SLOT (or either is in @world).
If you want it not there, you have to make sure the deps explicitly
state it.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-07-30 9:50 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 [this message]
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
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=20120730115032.105ccb91@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=djc@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=ryao@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