[MacPorts] #54853: Using configure.ccache=yes on the commandline overrides portfile configure.ccache=no

[MacPorts]

#54853: Using configure.ccache=yes on the commandline overrides portfile
configure.ccache=no
--------------------+-----------------
 Reporter:  RJVB    |      Owner:
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  base    |    Version:
 Keywords:          |       Port:
--------------------+-----------------
 I just discovered that using `configure.ccache=yes` on the commandline to
 use the built-in ccache support on a punctual basis can break the build of
 ports that are incompatible with this feature and that thus set
 `configure.ccache no` in their portfile (or in the case of ports using
 CMake, in the portgroup).

 I can see how commandline `foo=baz` specifications need to override the
 value set via

 {{{
 options foo
 default foo bar
 }}}

 but there are clearly cases where this shouldn't happen when a value is
 set explicitly, even if that value is equal to the default.

 Maybe add a -force option to options variable, so the aforementioned ports
 can force a feature setting instead of having to detect and raise errors?

 {{{
 configure.ccache -force no
 }}}

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