> -----Original Message-----
> From: Vincent Lefevre [mailto:vincent+svn_at_vinc17.org]
> Sent: Saturday, January 17, 2009 8:24 PM
> To: users_at_subversion.tigris.org
> Subject: Re: SVN properties keywords
> Even on Unix, svn or svnversion are not necessarily available at
> build time, e.g. if the working copy is on a network file system
> and svn is available only on some machines. Hence the method I've
> suggested in another mail.
> Sent: Wednesday, January 14, 2009 9:20 PM
> I would like to have a svn:keywordseverytime for example.
> Every file that has this property set, will always be updated
> when there is a change in the repository, even when the file itself
> is not changed. So for example an $Id$ or
> $Revision$ in it, will always be up to date. I would call it then
> not $Revision$, but something like $BiggestRevision$ or so.
You're trying to fix a Configuration Management problem in your version
control tool. It's not going to work.
At a minimum you need to:
a) develop a build process that pulls code by SVN_URL+REV from
Subversion and does a build in a clean workspace,
a1) your build script can embed or set the SVN_URL+REV number in
your generated binaries
b) lock down your build box(es) in order to ensure that:
b1) compilers are standardized (and checked in,)
b2) that environment settings are controlled (batch and shell scripts
set ENV vars, .profiles, ENV scripts and build scripts are checked in,
b3) that a controlled version of subversion is installed on the build
c) develop and automated deployment process. If you have a lot of loose
files, deploy you app as a tar/jar/zip file and put a version.txt file
in the jar/tar/zip.
d) develop an audit process/script to verify that the deployed files are
correct (compare the deployed files against the files in the tar/jar/zip
at a minimum.)
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-20 23:28:21 CET