Hi,
I would say the situation with 10.15 is now similar to other OSes. Some
things work, some things do not. There are also some clear cases of
things not working, and cannot/willnot be fixed, such as 32 bit support.
At the end of the day though only you know which ports you really care
about, and cannot live without, so you need to do your homework
yourself. Identified those ports and then check their status at
https://ports.macports.org/
Finally, as with any major OS update, I strongly recommend making a full
bootable clone of your current system, before doing anything. Then, if
worst comes to work, reverting back is trivial. I recommend this for any
OS update, not at all specific to MacPorts...
Chris
On 09/01/2020 1:50 pm, joerg van den hoff wrote:
I had to upgrade to 10.15 (wanted to postpone this further but ...) and
recall that there were many reports over the last months of problems
with subsequent macports upgrade, recommendations to use previous xcode
releases with catalina and assorted package specific problems simply not
being solvable right now.
I have looked at the mail archive and macports webpage but have not
found a clear recommendation or statement what the current situation (as
of jan 2020) is.
so simple question: is it save/recommended to use current xcode (11.3)
when doing the usual macports migration routine? are there guaranteed
problems in certain packages/areas? or is everything back
to normal (most things will work, some might not...)?
thank you
