Re: [gentoo-python] Re: [PATCH python-ebuilds] python2.7: first ebuild converted to python-utils-r1.

[Michał Górny]

On Mon, 26 Nov 2012 11:23:32 -0500
Mike Gilbert <floppym@g.o> wrote:

> On Mon, Nov 26, 2012 at 2:58 AM, Dirkjan Ochtman <dirkjan@×××××××.nl> wrote:
> > On Wed, Nov 21, 2012 at 9:36 PM, Michał Górny <mgorny@g.o> wrote:
> >> Please review these changes. I will send a detailed note about
> >> the particular changes I've made in a reply to this mail.
> >>
> >> The general changes are:
> >>
> >> - clean up, update, getting rid of python.eclass implicity,
> >>
> >> - the compiled modules are now part of the package (as with other
> >>   python-r1 suite ebuilds),
> >>
> >> - an additional 'epython' module is installed which could be used to
> >>   quickly get the correct 'EPYTHON' value for the current Python
> >>   implementation (it will be used in python-exec's .py support).
> >
> > Sorry for being a bit late to the party.
> >
> > Has Mike looked at this already?
> >
> > Would it make sense to split this patch up? One patch for EPYTHON, one
> > patch for the compiled stuff changes, one patch for EAPI fixes (all
> > the || die stuff) and one patch for miscellaneous cleanups?

I can try splitting this one up but TBH I feel like it's a bit
of unnecessary additional work.

> >
> > Also, gentoo-dev might have some things to say about making a @system
> > dep EAPI=4, IIRC?
> >
>
> The EAPI bump is my main issue as well. We could just keep an old
> ebuild around for a while (perpetually?) to help people with really
> outdated systems.
>
> Otherwise, it looks ok to me.

This has been brought up before, and I think that keeping the old
ebuilds should suffice migrating those systems.

I'm not sure if there is a need to restrain from EAPI 4 any longer.
Well, maybe not necessarily from 4; but using EAPI older than 3
resulted in really ugly ebuilds.

-- 
Best regards,
Michał Górny