[MacPorts] #53284: shouldn't pre-configure be skipped when `use_configure no`?

[MacPorts]

#53284: shouldn't pre-configure be skipped when `use_configure no`?
--------------------+-----------------
 Reporter:  RJVB    |      Owner:
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  base    |    Version:
 Keywords:          |       Port:
--------------------+-----------------
 It's all in the title: shouldn't pre-configure (and post-configure) blocks
 be skipped when `use_configure no`? They should be irrelevant, and could
 cause undesirable side-effects.

 It may sound surprising that you'd run into the question. In practice it
 is in fact perfectly possible when a Portfile has one or more stub
 subports, either because the file provides a pre-configure itself for the
 main port (subports), or because a PortGroup does (e.g. the qmake5 and
 cmake-1.1 PGs).

--
Ticket URL: <https://trac.macports.org/ticket/53284>
MacPorts <https://www.macports.org/>
Ports system for macOS