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