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