On 5/7/22 14:24, [email protected] wrote:
> 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!


I did read the news item and set the systems as above with multiple
python targets - there is no mention of python-exec and its role in
which python version is in use for packages that just call "python". 
Perhaps I should have been clearer - what I see is with multiple python
targets present the python ebuild automatically selects the latest
version that is stable via python-exec - ok, some would want that.  But
what it should do is respect the users choice of running version and not
automaticly overide it without asking.  It looks like python-exec is the
controlling factor so I'll try CONFIG_PROTECTon that file and manually
manage it via ansible.

BillK

Reply via email to