[MacPorts] #62881: gcc11: port is deactivating libgcc10, resulting in broken dependent ports

[MacPorts]

#62881: gcc11: port is deactivating libgcc10, resulting in broken dependent ports
----------------------+--------------------------
  Reporter:  mascguy  |      Owner:  cjones051073
      Type:  defect   |     Status:  assigned
  Priority:  High     |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  gcc11    |
----------------------+--------------------------

Comment (by mascguy):

 Replying to [comment:26 cjones051073]:
 > I don't see how that could happen. The updated libgcc10 has an increased
 epoch, which is what the check in libgcc11 checks to see if it needs to
 first deactivate libgc10. If you already had the latest libgcc10
 installed, then installing libgcc11 would not have touched it.
 >
 > Also note, updating libgcc10 without the corresponding libgcc11 update
 would have lead you to having no runtime installed at all, and most
 probably rev-upgrade would then trigger due to missing libraries. For this
 reason I find it hard to believe this is actually the situation you where
 in.

 I can't explain it, but I can say this happened across all of my local
 setups: MacOS 10.12, 10.13, 10.14, and 10.15. In all four cases, the same
 issue occurred.

-- 
Ticket URL: <https://trac.macports.org/ticket/62881#comment:31>
MacPorts <https://www.macports.org/>
Ports system for macOS