On May 21, 2007, at 20:32, Matt Sickler wrote:
> On 5/21/07, 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)
> post-commit hooks wont work
Of course it could. Commit comes in which adds or updates an odt
file, post-commit hook extracts the xml from it and adds or updates
the xml in the next revision. Commit comes in which removes an odt,
post-commit removes corresponding xml.
> what you need to do is write a wrapper for svn that does the
> extraction and decomression (on commit) and compression and insertion
> (on checkout)
> it wont be easy, but its worth a shot
A wrapper would of course be another way this could be handled, but
would only work for command-line Subversion users; the post-commit
hook would work regardless of what client is used.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 22 05:52:26 2007