Re: [gentoo-python] [PATCH] Support overriding PYTHON_COMPAT.

["Nikolaj Sjujskij" <sterkrig@myopera.com>]

Den 2013-03-14 23:02:45 skrev Mike Gilbert <floppym@gentoo.org>:

> On Thu, Mar 14, 2013 at 12:15 PM, Michał Górny <mgorny@gentoo.org> wrote:
>> On Thu, 14 Mar 2013 17:10:26 +0400
>> "Nikolaj Sjujskij" <sterkrig@myopera.com> wrote:
>>
>>> Den 2013-03-13 23:49:33 skrev Michał Górny <mgorny@gentoo.org>:
>>>
>>>> It couldn't work properly, so I withdrawn it. The major problem is
>>> that
>>>> metadata becomes affected by environmental variables.
>>>>
>>>> Sadly, portage can't handle that nicely. Usually, it just results in
>>>> portage 'sticking' with one particular set of USE flags on the
>>> package
>>>> and trying to use the other one at the same time. In other words, a
>>> lot
>>>> of random behavior and QA warnings.
>>>>
>>>> Probably, the nearest thing that could work is PYTHON_COMPAT_OVERRIDE
>>>> which doesn't use the USE flags but instead forces all impls listed.
>>>   I see... Well, that's unfortunate, I hoped to test pylint with it,
>>> hacking ebuild just for changing PYTHON_COMPAT isn't much fun.
>>
>> Do you consider it useful enough if PYTHON_COMPAT_OVERRIDE affected
>> the build process only? Most importantly, visible USE flags
>> and dependency resolution wouldn't be affected.
>
> That sounds good enough to me. I usually do initial testing with the
> ebuild command anyway.
That's fine for developer, who can bump ebuild afterwards, but hacking  
ebuild just to report a bug and have your changes overwritten on the next  
sync is a bit annoying :)