We are currently using CVS to handle a pretty large project. We have a
bunch of MS Word documents that are versioned in the repository.
We are using an evil hack to update these documents when they are
committed to the repository (we're setting document properties to
$Author$, $Revision$ etc.) - this is done using a commit-script that
modifies the word-document on commit. Although probably pretty much
non-standard this actually works great. There is one usability draw-back
When the document have been commited to the repository by the user the
user must remove the document from the local repository and the issue a
'cvs update' to get the modified document from CVS (or do a 'cvs update
-C'). If the user don't do this he/she will get a conflict on the next
'cvs update' since the document on the server is different than the one
on the user's disk (although the same revision).
Now - looking at subversion - how would this issue be handled by
subversion? Is there some way to "push" the modified file back to the
client as a result of a successful commit?
As a parallell - suppose you have a simple text file with an $Id$ line, and
you modify the local copy, and the issue a commit, I suppose that the
keyword substitution for the $Id$ field is performed both on the server
and on the client (by the "server subversion process" and by the "client
subversion process")? IMO, this could be handled by the server only - on
a successful commit the server would send back a diff to the client
containing the modified keyword substitution line ($Id$). *If* the
commit worked this way, our ugly "Keyword substitution hack" would work
without the mentioned drawback...
Any comments on this?
P.S Please don't ask *why* we are doing this keyword substitution stuff
in MS Word files... ;) D.S
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Anders Engström firstname.lastname@example.org
. http://www.gnejs.net PGP-Key: ED010E7F
. [Your mind is like an umbrella. It doesn't work unless you open it.]
Received on Mon Sep 29 12:55:50 2003
- application/pgp-signature attachment: stored