Re: git: 988da7290c99 - main - ./UPDATING: mention the python default version change

On Tue 04 Jun 12:00, Gleb Popov wrote:
> I don't quite get what's being talked about here. I update PHP packages the
> same way as Python ones.
> 
> When I want to switch Nextcloud to a newer PHP version, I uninstall it,
> then do an autoremove sweep, then install a new one.
> 
> I just upgraded my Python packages the same way - remove old applications,
> autoremove deps, install the same applications with a new py311 prefix.
> 
> Getting conflicts is actually good there, as it either alerts me of a
> py39-only software or remove py39 leftovers.

except that without a pkg set, the number of conflicts is so huge that it
results in too complex problem for a solver to deal with and the outcome is it
proposes the user to delete half of kde for example or many other bad scenario
for the end user.

Perl upgrades and php upgrades do not generate such complicated issues because
the way they we deal with them in the ports tree is way more upgradable
friendly.

I don't know how this should be done with python, and maybe I should spend some
time diving into it, but clearly the way it is done now is not friendly and
something either on the technical side or the policy side should be done.

each time a procedure involves pkg set, it means we have not thought enough
about it to make it user friendly.

Best regards,
Bapt