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

Re: SVN equivalent for CVS history

From: Ken MacDonald <drken567_at_gmail.com>
Date: 2007-05-09 17:18:51 CEST

> SVN revisions become meaningless in your project if you have to say
> "This build was made from whatever projects we felt like updating and
> building at such-and-such a time". A more robust approach is to 'svn
> up' for every build (no room for missing anything, your tree is in a
> consistent state at a definite revision number), then teach your build
> system to build targets only when sources have changed.
> -Nathan

Teaching your build system to build targets when they have changed is
non-trivial. You not only have to worry about the file itself
changing, but whether its 'include' files have changed, or include
files that are included by the include files, and so on. Also,
changing options in a Makefile may require rebuilding targets as well
even if the source code itself is unchanged. I worked for some time in
a ClearCase-oriented environment, and their 'clearmake' product does a
fine job of build-avoidance, but is a fairly complex piece of s/w.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 9 17:19:09 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.