1 |
On Jul 30, 2012 9:04 AM, "Michał Górny" <mgorny@g.o> wrote: |
2 |
> |
3 |
> On Mon, 30 Jul 2012 08:11:09 -0500 |
4 |
> Matthew Summers <quantumsummers@g.o> wrote: |
5 |
> |
6 |
> > On Mon, Jul 30, 2012 at 6:56 AM, Dirkjan Ochtman <djc@g.o> |
7 |
> > wrote: |
8 |
> > |
9 |
> > > On Mon, Jul 30, 2012 at 11:50 AM, Michał Górny <mgorny@g.o> |
10 |
> > > wrote: |
11 |
> > > > Portage will pull python3 if and only if anything depends on |
12 |
> > > > python:3.* or anything depends on python without a SLOT (or |
13 |
> > > > either is in @world). If you want it not there, you have to make |
14 |
> > > > sure the deps explicitly state it. |
15 |
> > > |
16 |
> > > So how did python3 end up in the stages again, exactly? |
17 |
> > > |
18 |
> > > Cheers, |
19 |
> > > |
20 |
> > > Dirkjan |
21 |
> > > |
22 |
> > > |
23 |
> > Dirkjan, I believe it is portage that pulls in python:3, since by |
24 |
> > default it prefers the latest stable version. |
25 |
> |
26 |
> No. As you can see in the ebuild, it pulls python2 by default. To pull |
27 |
> in python3, you have to USE=python3. |
28 |
> |
29 |
> -- |
30 |
> Best regards, |
31 |
> Michał Górny |
32 |
|
33 |
So, what happens when you have neither USE python2 or python3 set, as that |
34 |
is the default. I think that pulls in the latest stable version. |
35 |
|
36 |
Matt |