[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 cjones051073):

 Replying to [comment:10 mascguy]:
 > Replying to [comment:9 cjones051073]:
 > > if reclaim is removing it then it is not being depended on by any
 installed port.
 >
 > The port is being removed by `port reclaim` because it's been
 deactivated.
 >
 > Test locally please.

 I did, extensively. I installed all the (lib)gcc ports from before the
 gcc11 update, and then ran a regular 'port sync ; port upgrade outdated'.
 what happens is this

  - libgcc11 needs to be installed because libgcc now depends on it.
  - libgcc11 cannot be installed whilst the *current* libgcc10 is activated
 because it conflicts. this is why libgcc11 has to force deactivate it
 first.
  - once libgcc11 is installed port can carry on upgrading other ports,
 which should involve reinstalling the new libgc10, which no longer
 conflicts.

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