On 7/1/06, Petr Baudis <pasky@xxxxxxx> wrote:
Dear diary, on Thu, Jun 29, 2006 at 08:23:31PM CEST, I got a letter
where Junio C Hamano <junkio@xxxxxxx> said that...
It would have been a bit easier to swallow if this whole
machinery to build config.mk were somewhere under contrib/ (say
in contrib/autoconf), with an instruction to make an "opt-in"
symlink "ln -s contrib/autoconf/config.mk config.mk" for people
who want to use it in the toplevel INSTALL file, perhaps.
Well, I don't get the point of that - it doesn't make any sense to me to
require this.
The point of ./configure is to make things easier for the user, so to
balance that we should make the ./configure harder to _call_ by requiring
the user to do strange arbitrary steps after calling it.
Easiest way is to output ./configure result to e.g. configure.mak.autoconf,
and include this file just before configure.mak in main Makefile.
Just as in patches (although you have to discard or revert two alternate
mechanism patches)
--
Jakub Narebski
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html