On Mon, 2002-08-05 at 07:40, Mats Nilsson wrote:
> The trouble of doing a combination of 'svn info' and 'sed' to patch the
> source code as a build step, is that svn will not recognize these changes
> as simple keyword substitutions. It will think that the file has changed,
> even though it hasn't (in a logical sense), and the file will get checked
> in in a changed state, upset merges and diffs and whatnot.
For what it's worth, I'm perfectly happy with the file being generated
from a script as part of my source-release procedure. This is what
happens with your ./configure script, after all - when you create the
source release, you run autoconf/automake/etc to create it. The file
need not be placed in the svn repository at all, just as ./configure
isn't.
For what it's worth, the only thing I would like to see to aid
auto-builds is some form of "svn info --revision" or "svn info
--format='%{REVISION}'" or similar. I have no preference as to which,
although the latter would probably be easier for Windows folks, and
makes no difference to UNIX folks. Either is, of course, not essential.
Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 13:00:48 2002