You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Christian Gudrian <Ch...@gmx.de> on 2005/01/18 22:20:43 UTC
Force commit
Hello, there!
Is it possible to force Subversion to commit a certain file everytime
"svn commit" is performed, regardless whether that particular file
contains any changes?
Reason: I want a local file (version.h) to contain the most recent
repository revision (which can then be referenced throughout the whole
program).
Any ideas how to accomplish this?
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Force commit
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
On Wed, 19 Jan 2005, Christian Gudrian wrote:
> > The svnversion command can generate such a file. You could integrate that
> > into your build system,
>
> I would like the version file to be a part of the repository, so that
> exported source trees with no access to the repository still compile.
>
What about generating the file at export time? (You could generate the
file during build if in the WC (svnversion doesn't need access to the
repo) and just use the included file if you are in an exported tree. It
gets a little complex. Maybe someone else has a simpler idea:-)
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Force commit
Posted by Christian Gudrian <Ch...@gmx.de>.
Hello, Peter!
> The svnversion command can generate such a file. You could integrate that
> into your build system,
I would like the version file to be a part of the repository, so that
exported source trees with no access to the repository still compile.
> but it may force a full recompile after every
> commit if you include it everywhere...
Basically the real setup is a little bit more complicated. I compile a
small library which exposes the version information to the outer world.
It's the only module that needs to be recompiled after a commit.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Force commit
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
On Tue, 18 Jan 2005, Christian Gudrian wrote:
> Reason: I want a local file (version.h) to contain the most recent
> repository revision (which can then be referenced throughout the whole
> program).
>
The svnversion command can generate such a file. You could integrate that
into your build system, but it may force a full recompile after every
commit if you include it everywhere...
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org