From: Ben Rockwood <benr@cu...> - 2002-11-29 20:16:58
Does anyone have a reason against removing configure.ac from the
repositories?All "modern" versions of the autotools want configure.in over configure.ac.
Any reason to keep the .ac's around?
//Ben Rockwood - UNIX Systems Admin
//-> We do what we can, We give what we have,
//-> Our doubt is our passion, and our passion is our task,
//-> The rest is the madness of Art.
//-> -Henry James
From: Kevin Brosius <cobra@co...> - 2002-11-29 21:30:57
Ben Rockwood wrote:
> Does anyone have a reason against removing configure.ac from the
> repositories?All "modern" versions of the autotools want configure.in over configure.ac.
> Any reason to keep the .ac's around?
We haven't covered this in a while :)
Last I remember at least a couple of the packages had different .ac and
.in files so that they would work with the newer and older autoconf. As
I recall the .ac will be used with a warning by newer autoconf if both
.ac and .in exist (whick makes me wonder what you mean by "modern".)
Older autoconf doesn't know about .ac and only uses .in. At least for
e17/apps/e those two are different and are supposed to allow building
with twop different versions of autoconf.
The last time one of the two was removed, people complained. I don't
know if anything has changed or not.
Get latest updates about Open Source Projects, Conferences and News.