^config\. is in .hgignore, bug config.h.in is tracked. It is autogenerated, shouldn't it be removed from repo?
On Fri, Dec 14, 2012 at 01:10:11PM +0000, Jeremy Henty wrote:
p37sitdu at lavabit.com wrote:
^config\. is in .hgignore, bug config.h.in is tracked. It is autogenerated, shouldn't it be removed from repo?
Yes, it should.
I'm not sure (my fault ;), but in practice: If removing it from the repo doesn't prevent "autogen.sh", from building "configure"; and the "./configure; make" dance works as usual, it should be ok to remove. -- Cheers Jorge.-
On Fri, Dec 14, 2012 at 10:34:13AM -0300, Jorge Arellano Cid wrote:
On Fri, Dec 14, 2012 at 01:10:11PM +0000, Jeremy Henty wrote:
p37sitdu at lavabit.com wrote:
^config\. is in .hgignore, bug config.h.in is tracked. It is autogenerated, shouldn't it be removed from repo?
Yes, it should.
I'm not sure (my fault ;), but in practice:
If removing it from the repo doesn't prevent "autogen.sh", from building "configure"; and the "./configure; make" dance works as usual, it should be ok to remove.
On top of config.h.in there is a comment that says "Generated from configure.in by autoheader". "./autogen.sh; ./configure; make" works after removing config.h.in. By the way, configure.in is named configure.ac now. [1] autoconf shows a warning each time it sees configure.in. [1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Writing-Autoconf-...
p37sitdu wrote:
By the way, configure.in is named configure.ac now. [1] autoconf shows a warning each time it sees configure.in.
[1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Writing-Autoconf-...
I believe there was some discussion of this in the past, with some concern about still working with old versions of autoconf that one could reasonably expect someone to still have around somewhere. When was the renaming done?
On Fri, Dec 14, 2012 at 05:36:42PM +0000, corvid wrote:
p37sitdu wrote:
By the way, configure.in is named configure.ac now. [1] autoconf shows a warning each time it sees configure.in.
[1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Writing-Autoconf-...
I believe there was some discussion of this in the past, with some concern about still working with old versions of autoconf that one could reasonably expect someone to still have around somewhere. When was the renaming done?
Tue, 17 Jul 2001 07:53:06 http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=f0478c4702efe2...
p37sitdu wrote:
On Fri, Dec 14, 2012 at 05:36:42PM +0000, corvid wrote:
p37sitdu wrote:
By the way, configure.in is named configure.ac now. [1] autoconf shows a warning each time it sees configure.in.
[1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Writing-Autoconf-...
I believe there was some discussion of this in the past, with some concern about still working with old versions of autoconf that one could reasonably expect someone to still have around somewhere. When was the renaming done?
Tue, 17 Jul 2001 07:53:06
http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=f0478c4702efe2...
I, for one, would feel okay with changing it, then...
On Fri, Dec 14, 2012 at 06:46:16PM +0000, corvid wrote:
p37sitdu wrote:
On Fri, Dec 14, 2012 at 05:36:42PM +0000, corvid wrote:
p37sitdu wrote:
By the way, configure.in is named configure.ac now. [1] autoconf shows a warning each time it sees configure.in.
[1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Writing-Autoconf-...
I believe there was some discussion of this in the past, with some concern about still working with old versions of autoconf that one could reasonably expect someone to still have around somewhere. When was the renaming done?
Tue, 17 Jul 2001 07:53:06
http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=f0478c4702efe2...
I, for one, would feel okay with changing it, then...
+1 -- Cheers Jorge.-
participants (4)
-
corvid＠lavabit.com -
jcid＠dillo.org -
onepoint＠starurchin.org -
p37sitdu＠lavabit.com