ignore pdf "created" date

["Jan-H. Jagla" <jh...@gams.com>]

Hi all,

I searched the users list but didn't find a solution for this problem:

We have pdf files which are automatically created but very often are not 
changed at all. However, the pdf file property "created" gets a new 
date, so the whole binary file shows up as modified and thus will have 
to be committed back into the repo.

Is there a way to automatically ignore commits of pdf files where only 
the pdf properties are changed but nothing of the real content?

Thanks in advance!
Jan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: ignore pdf "created" date

[Andy Levy <an...@gmail.com>]

On 6/29/07, Jan-H. Jagla <jh...@gams.com> wrote:
> Hi all,
>
> I searched the users list but didn't find a solution for this problem:
>
> We have pdf files which are automatically created but very often are not
> changed at all. However, the pdf file property "created" gets a new
> date, so the whole binary file shows up as modified and thus will have
> to be committed back into the repo.
>
> Is there a way to automatically ignore commits of pdf files where only
> the pdf properties are changed but nothing of the real content?

As far as Subversion is concerned, those properties *are* part of the
content. Subversion doesn't understand semantics, it only understands
that something inside the file changed.

Why do you have a process which creates/updates PDFs with no material
change in the first place? Fix that, and Subversion won't pick the
files up as changed.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: ignore pdf "created" date

[Greg Thomas <th...@omc.bt.co.uk>]

On Fri, 29 Jun 2007 11:38:38 -0400, "Jan-H. Jagla" <jh...@gams.com>
wrote:

>We have pdf files which are automatically created but very often are not 
>changed at all. However, the pdf file property "created" gets a new 
>date, so the whole binary file shows up as modified and thus will have 
>to be committed back into the repo.

My first answer is no; the file has changed and you can't expect svn
to magically know that the bit of the file that has changed is of no
use to you. You should really change you automatic generation of PDF
files so that they are not re-generated if there is no need; e.g.
using a make file. This is analogous to a compiled program; you only
recompile the .c to the .o if the .c file has actually changed.

My second answer begins "however". However, there was some talk of
custom svn keywords. I forget what happened to those, but if it were
possible to create a custom svn keyword such that it looked like the
binary form of the PDF created property, then it may be possible, in
much the same way that svn does not consider a manual change to the
$LastChangedDate keyword a committable change.

Greg
-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org