Created attachment 599320 [details, diff] Add USE=pump With distcc-pump support being removed from portage itself (bug #702146) it would be good to not have to install that part at all, as it's currently the only thing on all my systems pulling in python 3.6. Attached is an ebuild patch that implements this. The configure script has a --disable-pump-mode flag but unfortunately it doesn't do anything.
(In reply to Anthony Parsons from comment #0) > Created attachment 599320 [details, diff] [details, diff] > Add USE=pump > > With distcc-pump support being removed from portage itself (bug #702146) it > would be good to not have to install that part at all, as it's currently the > only thing on all my systems pulling in python 3.6. > > Attached is an ebuild patch that implements this. The configure script has a > --disable-pump-mode flag but unfortunately it doesn't do anything. Thanks. I'm going to review and merge it later today. While at it, could you report it upstream that the option doesn't do anything? ;-)
I'm not sure if it's really worth. We still need Python because of other Python scripts. If we need Python anyway, then having a flag not to install a few Python modules doesn't seem very useful.
(In reply to Michał Górny from comment #2) > I'm not sure if it's really worth. We still need Python because of other > Python scripts. If we need Python anyway, then having a flag not to install > a few Python modules doesn't seem very useful. Yeah, I don't have strong feelings about it either way and the work required feels kind of hacky. Bumping PYTHON_TARGETS up to 3.7 would be an easier way to achieve the same end result - upstream already seems to support that (but not 3.8). If that sounds better, go ahead and reject this.
Heh. Actually, the main reason I didn't add new impls yet is because I don't use pump and I haven't figured out yet how to sanely test it.
