[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:7 mascguy]:
 > Replying to [comment:6 cjones051073]:
 > > ok, but even then it is fine as `libgcc10` now depends on `libgcc11`
 (via `libgcc`) so once the update is complete then will still get the
 complete gcc10 runtime.
 > >
 > > no, `libgcc10` is not removed, it is required to satisfy the
 dependency tree.
 > >
 > > This behaviour is all by design, to ensure all gcc ports share the
 same consistent runtime.
 >
 > By deactivating `libgcc10`, the port is subsequently removed by `port
 reclaim`. So yes, you are breaking dependent ports.
 >
 > Please fix this...

 if reclaim is removing it then it is not being depended on by any
 installed port.

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