Joshua Varner wrote:
...
> On 12/6/05, Andy Levy <andy.levy@gmail.com> wrote:
>
>>On 12/6/05, Joshua Varner <jlvarner@gmail.com> wrote:
>>
>>>On 12/6/05, Andy Levy <andy.levy@gmail.com> wrote:
...>>
>>Actually, I wasn't planning on changing the file in the commit. We'll
>>be keeping both the PDF and the source DOC in the project, in
>>different locations. My plan was to, in the post-commit or later,
>>export the updated DOC file to a temp directory, convert it to PDF,
>>then check the PDF in at the proper location.
>
> It might be easier to have a hook script that rejects any commits that
> include a doc file, but not the corresponding PDF. Then providing a
> little commit wrapper script to do the conversion if necessary, prior
> to commiting.
Yet another option for this is to use CruiseControl.Net to monitor changes to
DOC files and do the update there. That's the way I'd do it, but I'm already
deploying CruiseControl.Net. The advantage is that the user doesn't have to
wait for the post-commit hook. The disadvantage is that the window of time when
the .doc and .pdf are out of sync is a bit large, depending on the
configuration. (Plus the obvious disadvantage of yet another tool, if you have
no other use for CC.Net.)
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 7 14:50:45 2005