[MacPorts] #59289: base does not necessarily tell you when circular dependency occurs

[MacPorts]

#59289: base does not necessarily tell you when circular dependency occurs
-----------------------+--------------------
  Reporter:  fvaccari  |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  base      |    Version:
Resolution:            |   Keywords:
      Port:            |
-----------------------+--------------------

Comment (by cjones051073):

 Replying to [comment:8 jmroot]:
 > Replying to [comment:6 cjones051073]:
 > > Although in this case it was not really the port itself causing the
 problem, but base itself through the compiler selection it was making.
 >
 > Technically that choice comes from the ports tree, not base.

 In this case the cmake port did not have a problem until an unrelated
 change elsewhere was made, adding a new compiler option. I find it hard to
 blame the port in this case.

 In any case it really does not matter, assigning ‘blame’ is useless. The
 bottom line there is one place that could ever detect these circular
 dependencies, and that is in base, so that is the place that needs the
 protection or error reporting.

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