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

On Tue 04 Jun 12:14, Baptiste Daroussin wrote:
> 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

Self replying: example of impossible solving issues generated by the current
policy in python world

let say you have py39-mutagen and py39-matrix-synapse installed.

There is absolutly no way for pkg to discover that because default python was
changed to python 3.11 then those package should now be named py311-mutagen and
py311-matrix-synapse.

Which means the solver will current propose to remove them and all they depend
on, as they do not exist anymore in remote repositories, or if we have stronger
rules than we have now pkg will die in a non solveable situation and let the
user try to figure out what should be done.

This is our role as ports committers to find something which don't let users be
trapped in such situation.

Best regards,
Bapt