On Mon, Feb 28, 2011 at 12:13:22PM -0800, Toshio Kuratomi wrote:
If people have additional reasons that macroizing all directory paths
sense, please let us know (here or as a comment in the ticket). Then FPC
can decide whether to relax this rule or update the rule with information
about why we have it in place.
The point of the macros is to ensure consistent use of paths between
the configure, install, and packaging stages so that builds don't
break if there are changes in any part of the chain.
%configure uses those macros. If spec files were allowed to not use
the macros, then changes to %configure would break the spec files. So
if you are going to remove the requirement for the macros in spec
files, then the behavior of %configure should not be reliant on the
macros either. In fact, all use of such macros should be removed (not
disallowed, but removed from use in the standard build macros).