[MacPorts] #54028: Gawk fails to update after readline update

[MacPorts]

#54028: Gawk fails to update after readline update
-------------------------------+-------------------------
  Reporter:  augustusjdporter  |      Owner:  Schamschula
      Type:  defect            |     Status:  closed
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:
Resolution:  fixed             |   Keywords:
      Port:  gawk              |
-------------------------------+-------------------------

Comment (by ryandesign):

 gawk already got a revbump in [44840c49dbb96941fe5dfd27eba5f6aa3d954fd8
 /macports-ports]. Doing it a second time fixes nothing.

 The problem is that standard configure scripts, such as the one gawk uses,
 automatically check for common utilities like gawk which are used during
 the build process. So when trying to rebuild gawk with the new readline,
 gawk's configure script finds the already-installed broken copy of gawk,
 and tries to use it during the build, which fails. The solution is to
 deactivate gawk, then upgrade gawk.

 {{{
 sudo port -f deactivate gawk
 sudo port -u upgrade gawk
 }}}

 There's not really anything we can do to automate this fix. We could use
 the conflicts_build portgroup to indicate that gawk is incompatible with
 itself, but that would only be necessary in the unusual circumstance where
 the already-installed gawk is broken due to a new major version of one of
 its dependencies; it would be an unnecessary inconvenience other times. It
 also wouldn't help the thousands of other ports whose configure scripts
 will opportunistically use MacPorts gawk if it is installed.

 If we could figure out a way to tell gawk's configure script to always use
 /usr/bin/awk even if /opt/local/bin/gawk is installed, that would be a
 good step. I feel like we tried to figure that out before and failed.

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