Re: [gentoo-python] Python 3 in Gentoo

[Mike Gilbert]

On Mon, Jul 30, 2012 at 11:40 AM, Dirkjan Ochtman <djc@g.o> wrote:
> On Mon, Jul 30, 2012 at 5:30 PM, Mike Gilbert <floppym@g.o> wrote:
>>> I guess I still think it should be possible to give Portage a hint not
>>> to install a new SLOT if the old SLOT is okay.
>>
>> In this case, I think we would need something more subtle than that;
>> most users would want a hypothetical python-2.8 to be installed, and
>> python-3 users will certainly want to be upgraded to python-3.3 when
>> that lands.
>>
>> In other words, if we tell portage not to upgrade to a new slot
>> automatically, that means users would have to manually install each
>> major release of python.
>
> No, I was going for the kind of effect where being inclusive wrt the
> new major Python version would be controlled in a single place. I.e.
> in the ebuild or in an eclass or some such.
>
> So you'd have SLOT="~3" in the python-3* ebuilds, and Portage would
> know to not install SLOT=3 unless requested explicitly, and at some
> point we'd remove the '~'.

Where else in the tree could this concept be applied?

I would prefer to avoid going through the EAPI process if it is just
going to be used for python. And even then, I'm not really excited
about the prospect of explaining it.

Also, I'm sure that people will whine about the "upgrade path" being
broken if we set EAPI=5 or 6 in the python ebuilds any time this
decade.

A solution that works within the confines of the current EAPI spec
should be greatly preferred.