svn commit: r520219 - in head/Mk: . Uses

[Mathieu Arnold]

On Tue, Dec 17, 2019 at 12:00:40AM +0100, Christoph Moench-Tegeder wrote:
> ## Matthias Fechner (idefix at fechner.net):
> 
> > it seems that this commit cause now that all python 3.6 related ports
> > are deinstalled if you execute:
> 
> Indeed does "pkg upgrade" handle flavored ports rather ungracefully
> when the default flavor changes (like in this case, where the default
> python version changed and took the flavor with it).
> 
> As far as commit logs serve, this is the first time a python default
> version has been bumped since the introduction of FLAVORs (switch to
> 3.6 as the default for python3: 2017-04-28, FLAVORs: 2017-11-30).
> 
> -> bapt@, you wanted to know when "pkg upgrade" results in an
> undesirable state? This would qualify, I think. At least, it should
> be handled nicer. I'm not sure how to make this "right" (not familar
> with the code, not even tried looking at it, I admit), but is it
> even possible to detect such FLAVOR change and upgrade manually
> installed packages to the new flavor and handle dependencies accordingly?
> 
> In two weeks plus build time this will hit quarterly and with that
> many more users who are "just using packages" - I'd imagine there
> would be even more surprised (not in a good way) people.

I ran this to prevent sillynesses:

for i in $(pkg query -g %n 'py36*'); do pkg set -yn $i:${i/36/37}; done

-- 
Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20191217/75829de9/attachment.sig>