|
From: | Ivan Vučica |
Subject: | Re: Policy on checking in rebuilt configure |
Date: | Mon, 5 May 2014 16:42:46 +0100 |
Not sure whether we need a new policy here. There is the simple rule that when you change configure.ac you also need to regenerate configure and check it in.
As far as I remember there was only one case in recent years where somebody didn't follow the rule but checked in a manually changed configure file.
Not having configure checked in is an option but it requires one additional tool installed on every machine where GNUstep is build. And it breaks the expectation that "configure; make; make install" builds a usable system.
It would be nice if we standardised on using the most recently released autoconf, in order to keep diffs of the configure files to a minimum (I understand your distaste for large diffs).
BUT ... nobody really needs to review changes to configure, since it's trivial to regenerate it if there's a faulty/corrupt commit; so I don't think it's anything to worry about if we have occasional large diffs in the configure scripts.
[Prev in Thread] | Current Thread | [Next in Thread] |