Thanks for all of the thoughts and replies. To summarize we are distributing our code directly from the repository but don't think that every platform should be required to have the same set of autotools that we have, so we commit the bootstrap generated files. It seems to me that the autotools themselves are not that portable - the resulting configure file and *.in files are - and when I think about providing support I would much rather support those resulting files on a new platform than the tools that built them. But due to issues of make determining dependencies based on timestamps this doesn't exactly work. Isn't there a way to tell automake, perhaps through the Makefile.am, to remove or ignore these particular dependencies? If not is it worthy of a new feature request? I know, I know - I should write to the automake list :-). Thanks, Jim On Mon, Jun 20, 2011 at 6:28 PM, Harlan Stenn <stenn@xxxxxxx> wrote: > If auto*-generated files are being checked in to a repo, you may be > seeing a problem where the timestamps of those files are not kept in > "relational" order when you check out a copy from the repo. > > I think your choices are to either live with it (just like the way Eric > wrote) or run a script after checkout that "touches" the > generated files in the correct order so that the dependency order is > maintained. > > If you want an example of this, check out a tarball of NTP and look at > the top-level "bootstrap" script. Be advised that NTP's need and use > for this is probably quite a bit more involved that what you might > need. > > -- > Harlan Stenn <stenn@xxxxxxx> > http://ntpforum.isc.org - be a member! > _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
