[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:  closed
  Priority:  Normal   |  Milestone:
 Component:  base     |    Version:
Resolution:  invalid  |   Keywords:
      Port:           |
----------------------+--------------------

Comment (by RJVB):

 I see you point, but is it really valid? Shouldn't alternative
 configuration systems ideally redefine `configure.cmd` and provide their
 own `configure` if they have to? The way I interpret `use_configure no` is
 that it turns off the configuration step altogether because it's unneeded
 or unwanted, for projects that come with a preexisting Makefile, use
 xcodebuild or don't build anything.

 It's been ages since I used xmkmf but IIRC it stands for "X Make Makefile"
 and is/was a precursor to autoconf and cmake etc. So you'd do

 {{{
 > xmkmf
 > make
 }}}

 Is the `autoreconf` setting respected when you set `use_configure no`?

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