Tom Lane wrote: > Why not? The shipped tarball would contain exactly the same > pg_config.h.win32 it does today; the only difference is that the > version info would've been inserted automatically instead of > manually.
I suggest you do it in a makefile as part of the distprep target. distprep: pg_config.h.win32 pg_config.h.win32: pg_config.h.win32.in sed 's/@VERSION@/$(VERSION)/g' $< >$@ maintainer-clean: rm -f pg_config.h.win32 That way we don't bother every configure runner with the issue. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly