[MacPorts] #32542: Setting configure.compiler to a MacPorts-provided compiler doesn't add dependency automatically

[MacPorts]

#32542: Setting configure.compiler to a MacPorts-provided compiler doesn't add
dependency automatically
---------------------+----------------------
  Reporter:  cal@…   |      Owner:  larryv@…
      Type:  defect  |     Status:  assigned
  Priority:  High    |  Milestone:
 Component:  base    |    Version:  2.0.3
Resolution:          |   Keywords:
      Port:          |
---------------------+----------------------

Comment (by cal@…):

 `hijack_option` does change the semantics of `depends_lib` and
 `depends_build`. Although it probably doesn't make a difference in most
 cases we should consider doing this without this hack. If we had a
 callback that would be evaluated after the Portfile (and all variants)
 were completely sourced, we could add the correct compiler dependency
 there using a simple `depends_build-append` statement.

 source:trunk/base/src/macports1.0/macports.tcl at 102897:1608-1618#L1608 is
 the relevant part of the code executing the Portfiles. Adding a callback
 there (e.g., `$workername eval add_compiler_dependencies`, which would in
 turn have to be created using `$workername alias add_compiler_dependencies
 actually_implementing_procedure`) seems like a cleaner solution to me and
 would avoid the change in semantics. We could also provide a generic
 callback mechanism there, just in case we (or a Portfile author) ever
 needs something similar.

-- 
Ticket URL: <https://trac.macports.org/ticket/32542#comment:30>
MacPorts <http://www.macports.org/>
Ports system for Mac OS