[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:20 mascguy]:
 > Replying to [comment:16 cjones051073]:
 > > Replying to [comment:13 mascguy]:
 > > > Okay, so why does `libgcc11` conflict with `libgcc10` in the first
 place? `libgcc8`, `libgcc9`, and `libgcc10` all coexist peacefully while
 active.
 > >
 > > It only temporarily conflicts whilst the upgrade is happening. Before
 the update libgcc10 provides the primary runtime, whilst after the update
 libgcc11 does. The problem is the update process tries to install the new
 libgcc11 before the old libgcc10 is updated, leading to a temporary
 situation where they conflict.
 >
 > Can you clarify what you mean by "before the old libgcc10 is updated?"

 Not really sure how else I can put it...

 The gcc ports are all self consistent, before and after the update. The
 problem is to get to the consistent state after the update *both* libgcc11
 and libgcc10 have to be updated. Now, things can only happen one at a time
 so if port decides to install libgcc11 before it has updated the old
 libgc10, then we hit this situation. The force deactivate resolves it.

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