Dnia 2022-07-05, o godz. 13:04:07 William Kenworthy <[email protected]> napisał(a):
> I synced portage a couple of days now and now my systems are
> rebuilding python modules for 3.10 without any input from me (prior
> to this 3.10 was on the system but wasn't picked up by applications.)
> This is breaking non portage apps like homeassistant which are still
> not fully 3.10 safe - ok that's sort of expected and in this case
> will be fixed, but I cant find anything definitive on the task of "I
> want to control which python is used" and when to update.
>
> I eventually found that changing the order in python-exec.conf helped
> on the homeassistant system. There is a LOT of out of date
> documentation out there, particularly with eselect being used but is
> actually not used with python anymore (why? - from a user point of
> view having consistent access to configuration is a no brainer!) - so
> how can one get python to behave reliably and override its automatic
> get things wrong installation system? Is manually editing
> python-exec.conf the way (which seems to get overwritten - shouldn't
> that be a protected config file then?)
>
> BillK
>
>
>
>
Hello!
In "eselect news" info about python update there is a paragraph about
blocking the upgrade. It just means adding:
*/* PYTHON_TARGETS: -* python3_9
*/* PYTHON_SINGLE_TARGET: -* python3_9
to /etc/portage/make.conf or /etc/portage/package.use or
/etc/portage/package.use/zz-somename - whichever suites you best.
You can also change these settings just for some packages, by adding:
cat/pkg PYTHON_TARGETS: -* python3_9 PYTHON_SINGLE_TARGET: -* python3_9
to one of aforementioned files.
Hope that helps!
--
xWK
pgp5vGReLrLfC.pgp
Description: Podpis cyfrowy OpenPGP
