So since configure supports VAR=VAL, since this is a perfect scheme
which is completely extendible, I was noting that this scheme was
enough to support all the foodir variables we might need.
We will stay with the --foo syntax for configure options. We should
not change the configure syntax incompatibly unless there is a
pressing need for a change.
I think that you are judging these issues as if you were working on an
ordinary software package. But actually we are talking about changes
in a long-established standard which hundreds or thousands of programs
follow. Incompatible change causes great harm and trouble regardless
of the details; it can only be justified if there is a very big
problem.
Even a compatible change such as requiring all programs to support the
--foodir or --dir-foo syntax would be a hassle for some programmers
(those who don't use Autoconf), and the change can take years to
complete.
| Perhaps we should start accepting --dir-foo as well as --foodir.
| This would increase consistency.
You choose, you're in charge of this.
Please start supporting --dir-foo as well as --foodir. That is upward
compatible so it is not harmful. It may take a few years to get into
all programs, but there is no hurry.
