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

Re: Is it possible to synchronize unpacked sources with its binary container?

From: Richard Bos <ml_at_radoeka.nl>
Date: 2007-05-22 09:49:25 CEST

On Mon, May 21, 2007 at 06:14:18PM -0400, Jim Sokoloff wrote:
> On Mon, 21 May 2007, Richard Bos wrote:
> >the situation is as follows, an svn repository that holds many binary odt
> >files. These are actually just binary containers with compressed xml
> >(text)
> >files. I very much would like to track the changes that are made to the
> >xml
> >files inside that binary odt file. To be more precise I'm only interested
> >to
> >follow the changes made to the file content.xml inside the odt binary
> >container. The advantage of the having the content.xml in the svn
> >repository
> >is that e.g. annotations can be shown, and that diffs made to the document
> >are automatically included in e.g. post-commit notification emails.
> You could get the behavior you want with a post-commit
> hook (that would have to handle the case of content.xml
> already existing, the delete of an odt file, etc)

Would this method still keep the same user assigned to the
modification? I don't think as the post-commit script is
executed on the server by the user that owns the svn server
process. I would like to keep the person that modifies
the document, for annotation....
> We have several external processes that are triggered
> as the result of commits (builds for specific branches,
> updates of shared development webservers, etc). This
> would be just another type of thing, and something for
> which the post-commit hook would work well for.

So the post-commit hook set a flag, after which a cronjob
sees the flag and does its thing? Or do you do it a
different way?

> (Note that you'd get TWO revision numbers, one for the
> odt and one for the .xml checkin. Don't try to modify
> the transaction from the post-commit-hook; you are too
> late. But, if they happen one right after the other, I
> doubt you care.)

See above, I want to keep the author's name unchanged.
> It's not as elegant a solution as building it into the
> client, but it's reasonably easy to implement, doesn't
> require patching the svn core, and works in all clients.
> As for the post-commit email, obviously you could change
> the post-commit hook to send the content.xml diff in one
> email if you wanted.

I use svnnotify and I want to keep on using this....

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 22 09:49:45 2007

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.