On Thu, 14 Mar 2013 17:10:26 +0400 "Nikolaj Sjujskij" wrote: > Den 2013-03-13 23:49:33 skrev Michał Górny : > > > 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. I asked Zac about a possibility of disabling cache conditionally to a variable but I don't think that reached anywhere. -- Best regards, Michał Górny