Re: Policy on checking in rebuilt configure

[Fred Kiefer]

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.

Fred

On the road

Am 05.05.2014 um 00:33 schrieb Ivan Vučica <address@hidden>:

Hi,

Do we have any policy on checking in rebuilt configure? Running autoreconf, of course, produces a large diff since I'm not using the same version as the previous committed; and keeping configure and configure.ac in sync manually is very painful.

Is there a significant reason why we should keep configure checked in in the first place? It is a generated file that is trivial to generate with autotools; while it should be in tarballs, it doesn't have to be checked in.

I'm specifically looking at gnustep-make right now, but since core libs all include configure scripts, this applies to all of them.

--

Ivan Vučica

address@hidden

_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev