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

Re: Version-value-in-source alternative proposal

From: William F. Dowling <william.dowling_at_thomson.com>
Date: 2006-01-26 15:08:16 CET

On Wed, 2006-01-25 at 23:29 -0600, Matt England wrote:
> At 1/25/2006 10:02 PM, Matt England wrote:
> >Here's another problem with the current
> ><http://subversion.tigris.org/faq.html#version-value-in-source> solution:
> More problems: the above example will force a program re-link every time
> 'make' is run. Ouch. (Am I the only one doing this stuff? I'm quite
> surprised that Subversion has gotten this far without these features.)

You are not the only one. I am currently evaluating subversion (for a
possible switch from CVS) and it is issues like these that give me
concern about making the move to svn. I also have grave concerns about
subversion's ability to handle dependent modules (the oft-written about
externals issues.)

> For those running more-advanced makefiles, I provide an excerpt of mine
> below (haven't proved it to be completely working yet with the svnversion
> stuff yet...but I think it's close) in the event this helps anyone else
> doing this.


> (I put the .cpp in the obj_dir...because it's nasty for my make process to
> update the working copy/repo...it's just bad. That's why I try to enforce
> a "read-only" policy on my source-file area, and only write to the bin,
> obj, lib, and pkg dirs in my builds.)

Of course. Doesn't everybody do that?

Will Dowling

William F Dowling
william.dowling .at. thomson.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 26 15:10:12 2006

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.