config.h.in

[p***@public.gmane.org]

^config\. is in .hgignore, bug config.h.in is tracked. It is
autogenerated, shouldn't it be removed from repo?

[Jeremy Henty]

Post by p***@public.gmane.org
^config\. is in .hgignore, bug config.h.in is tracked. It is
autogenerated, shouldn't it be removed from repo?

Yes, it should.

Regards,

Jeremy Henty

[Jorge Arellano Cid]

Post by Jeremy Henty

Post by p***@public.gmane.org
^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.

[p***@public.gmane.org]

Post by Jorge Arellano Cid

Post by Jeremy Henty

Post by p***@public.gmane.org
^config\. is in .hgignore, bug config.h.in is tracked. It is
autogenerated, shouldn't it be removed from repo?

Yes, it should.

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-Input

[corvid]

Post by p***@public.gmane.org
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-Input

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?

[p***@public.gmane.org]

Post by corvid

Post by p***@public.gmane.org
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-Input

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=f0478c4702efe203fc22617966c4e5b934b8a0dc

[corvid]

Post by p***@public.gmane.org

Post by corvid

Post by p***@public.gmane.org
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-Input

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=f0478c4702efe203fc22617966c4e5b934b8a0dc

I, for one, would feel okay with changing it, then...

[Jorge Arellano Cid]

Post by corvid

Post by p***@public.gmane.org

Post by corvid

Post by p***@public.gmane.org
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-Input

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=f0478c4702efe203fc22617966c4e5b934b8a0dc

I, for one, would feel okay with changing it, then...

+1