[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Building subversion with libtool 1.4

From: Paul D. Smith <psmith_at_gnu.org>
Date: 2001-07-03 23:47:06 CEST

%% Karl Fogel <kfogel@collab.net> writes:

  kf> If we keep autogenerated files, such as configure, under revision
  kf> control, people must manually remember to actually do the
  kf> regeneration before committing. (Attempts to automate this
  kf> requirement usually fall flat, because not *every* modification to
  kf> a `foo.in' file needs to result in a regenerated `foo' -- only
  kf> semantically important changes).

I'm not a Subversion developer, so take this as a comment from the
peanut gallery:

I've been involved with a project that decided to put configure,
Makefile.in, etc. in CVS and it was bad mojo. Very annoying. Stuff
broke all the time. Even more annoying than forgetting to rebuild the
files, on some systems these files would change for no apparent, or
important, reason, and then you'd get "dueling commits" where one person
would commit some changes that had nothing to do with configure/etc.,
but modified all the Makefile.in's in some meaningless way, then another
person would commit something that changed them all back, etc.

We took these files back out again after a few months of cursing (and
_that_ was hard, too, with CVS--can't wait for Subversion to be stable

What we did instead was create nightly snapshots using an automated
script that did a "cvs update" then "make dist" (basically), then the
resulting tar file was stuck into an anonymous FTP area.

If the script failed, email was sent to the devel list. This is a nice
feature in and of itself, to get a nightly sanity build.

We obviously made absolutely no comments concerning the reliability
etc. of the code in a given nightly snapshot; really the snapshots are
more for developers who don't have or want to install the development
tools--obviously these developers didn't do CVS commits since they were
working from a dist tarball; they would send patches to the committers
for application.

Just another idea...

 Paul D. Smith <psmith@gnu.org>          Find some GNU make tips at:
 http://www.gnu.org                      http://www.paulandlesley.org/gmake/
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:32 2006

This is an archived mail posted to the Subversion Dev mailing list.