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

On Tue, Jun 4, 2024, 13:14 Baptiste Daroussin <bapt@freebsd.org> 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.
>

Not really, thanks to autoremove step. Well, at least it is that way for me
and always been, so I never had to do pkg set -o

Anyways, this brings us back to the problem I tried to solve with the vital
flag. Somehow we should reject upgrade plans that try to remove
non-automatic and vital packages.