On Thu, Apr 25, 2013 at 10:22 AM, James K. Lowden <jklow...@schemamania.org>wrote:
> On Wed, 24 Apr 2013 19:17:32 -0700 > Dimiter 'malkia' Stanev <mal...@gmail.com> wrote: > > > > Why keep autoconf output in the source code repository? > > > > Maybe it's simply to guard from generating different ./configure > > files on each machine depending on what autotools were installed (I > > have very basic knowledge there so I could be wrong). > > The configure script is typically generated by a build machine that has > autotools installed, and included in a distribution tarball. The user > unpacks the tarball and runs the configure script. He doesn't need > the autotools and he doesn't generate the scirpt. > > Anyone building from the Fossil repository should IMO be prepared to > run autogen & co., and to have other ancillary tools ready as well. > > If that is so, then there is no harm in including ./configure from an older autoconf in the repo, since anybody who wants to build for an unusual platform that the older autoconf did not support can simply rerun autoconf. Right? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
