Re: [gentoo-user] Gentoo's Python policy drives me crazy
On Mon, Dec 16, 2019 at 2:07 PM Rich Freeman wrote: > > On Mon, Dec 16, 2019 at 2:00 PM Helmut Jarausch wrote: > > > > Today's updating involves some package which causes rebuilding > > a package which needs Python2.7 and another one which needs > > python_single_target_python3_8 > > required by that mysterious @__auto_slot_operator_replace_installed__ > > > > To emerge the Python2.7 package (Scribus) I do need to set > > PYTHON_SINGLE_TARGET="python2_7" > > in /etc/portage/make.conf > > which makes the whole update fail since the other packages needs > > PYTHON_SINGLE_TARGET="python3_8" > > > > So, what can I brave Gentoo user do? > > > > Set PYTHON_SINGLE_TARGET in package.env and not make.conf. That is > definitely a setting that can't be set globally. Alternatively, you can set it in package.use: app-office/scribus PYTHON_SINGLE_TARGET: python2_7 If the package supports several python versions, "-*" might come in handy. app-editors/vim PYTHON_SINGLE_TARGET: -* python3_7
Re: [gentoo-user] Gentoo's Python policy drives me crazy
On 12/16/19 2:00 PM, Helmut Jarausch wrote: Today's updating involves some package which causes rebuilding a package which needs Python2.7 and another one which needs python_single_target_python3_8 required by that mysterious @__auto_slot_operator_replace_installed__ To emerge the Python2.7 package (Scribus) I do need to set PYTHON_SINGLE_TARGET="python2_7" in /etc/portage/make.conf which makes the whole update fail since the other packages needs PYTHON_SINGLE_TARGET="python3_8" So, what can I brave Gentoo user do? Hopefully something better than trying to find which new package triggers which rebuild. PYTHON_SINGLE_TARGET for most set ups should default to python3_6 and PYTHON_TARGETS should be python2_7 and python3_6. scribus should be fine with the defaults, but if you really wanna deviate from default profiles, you'll probably have to set python_single_target_python2_7 manually for that package until it supports newer pythons. (currently it seems to support up to 3.7, it might support 3.8 as well, just hasn't updated, haven't looked into that detail)
Re: [gentoo-user] Gentoo's Python policy drives me crazy
On Mon, Dec 16, 2019 at 2:00 PM Helmut Jarausch wrote: > > Today's updating involves some package which causes rebuilding > a package which needs Python2.7 and another one which needs > python_single_target_python3_8 > required by that mysterious @__auto_slot_operator_replace_installed__ > > To emerge the Python2.7 package (Scribus) I do need to set > PYTHON_SINGLE_TARGET="python2_7" > in /etc/portage/make.conf > which makes the whole update fail since the other packages needs > PYTHON_SINGLE_TARGET="python3_8" > > So, what can I brave Gentoo user do? > Set PYTHON_SINGLE_TARGET in package.env and not make.conf. That is definitely a setting that can't be set globally. That said, the way python works on Gentoo certainly gets a lot of people confused. Also, just a heads-up that python 2.7 probably will be leaving the main repository in the next few weeks unless somebody steps up to maintain it. -- Rich
Re: [gentoo-user] Gentoo's Python policy drives me crazy
On Mon, Dec 16, 2019 at 08:00:41PM +0100, Helmut Jarausch wrote: > To emerge the Python2.7 package (Scribus) I do need to set > PYTHON_SINGLE_TARGET="python2_7" > in /etc/portage/make.conf > which makes the whole update fail since the other packages needs > PYTHON_SINGLE_TARGET="python3_8" You do not need to set anything in make.conf to build individual packages. For something like app-office/scribus you can put something like this in `/etc/portage/package.use`: app-office/scribus python_targets_python2_7 The issue of conflicting single targets solves itself if you don't set these options globally (in make.conf) and instead set them per-package as needed. signature.asc Description: PGP signature
[gentoo-user] Gentoo's Python policy drives me crazy
Today's updating involves some package which causes rebuilding a package which needs Python2.7 and another one which needs python_single_target_python3_8 required by that mysterious @__auto_slot_operator_replace_installed__ To emerge the Python2.7 package (Scribus) I do need to set PYTHON_SINGLE_TARGET="python2_7" in /etc/portage/make.conf which makes the whole update fail since the other packages needs PYTHON_SINGLE_TARGET="python3_8" So, what can I brave Gentoo user do? Hopefully something better than trying to find which new package triggers which rebuild.
