Re: [gentoo-python] python-r1 <-> python.eclass package dependencies

[Michał Górny]

On Sun, 11 Nov 2012 15:50:03 -0800
Brian Harring <ferringb@×××××.com> wrote:

> On Sun, Nov 11, 2012 at 01:35:20PM -0500, Mike Gilbert wrote:
> > On Sun, Nov 11, 2012 at 2:52 AM, Brian Harring <ferringb@×××××.com> wrote:
> > > So... thus:
> > >
> > > 1) make python.eclass know of both forms of USE_PYTHON (with periods,
> > > without).
> > > 2) convert USE_PYTHON to a use expanded target
> > > 3) convert python.eclass to use it.
> > >
> > > I realize this deprecates/kills PYTHON_TARGETS; my intention here
> > > isn't to piss on the var you added, it's to choose the less disruptive
> > > option here- lesser of two evils.  Starting from scratch,
> > > PYTHON_TARGETS would be fine- unfortunately we need to map existing
> > > users (and usage) from python.eclass into the replacement,
> > > constraining our choises a bit.
> > >
> > > Counter arguments?  To be clear, this is the path I strongly suggest
> > > we take- if you can punch holes in the logic/arguments from above, I'd
> > > definitely back down, but the use of PYTHON_TARGETS here feels like
> > > we're setting ourselves up for unnecessary pain.  Keep in mind not
> > > *all* of python.eclass notions/setup has to be chucked- we can
> > > translate certain parts of it across to ease developer/user pains.
> > >
> >
> > Following up on this and the irc conversation I eavesdropped on earlier:
> >
> > More recent versions of portage apparently filter USE_EXPAND
> > variables, so we can't utilize the old python abi values in USE_PYTHON
> > if we make that conversion.
>
> Just a note; portage's behaviour here, per the norm, is more stupid
> than that.  EAPIs 0-4 are supposed to /not/ have that filtering,
> meaning portage broke it's own behaviour again.
>
> I suspect we'll retroactively change EAPIs to compensate for this, but
> I don't know for a fact; the discussion for that will occur at
> https://bugs.gentoo.org/442830 .

I'm sorry if I miss something but don't EAPIs 0-4 define *no* behavior
for USE_EXPAND variables? (something around don't use them)

-- 
Best regards,
Michał Górny