[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: MikeW <mw_phil_at_yahoo.co.uk>
Date: 2007-05-10 09:46:01 CEST

Nathan Kidd <nathan-svn <at> spicycrypto.ca> writes:

> But Nikhil, I think you're approaching this problem from the wrong angle.
> If you have a requirement to build only solutions that have changed,
> then it should be the job of your build system to have proper
> dependencies and only build what has changed, based on what is on your
> disk (not parsing update logs).
> 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
I see the issue being that CVS's "compelling replacement" cannot do
(for whatever reason) something that CVS *could* do, which is unfortunate.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 09:47:10 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.