not merging dependent files, but versioning them anyway

[Mathieu Clabaut]

On Tue, Jun 23, 2009 at 21:39, da2 <dalist0 at gmail.com> wrote:

>
> Hello,
>
> I am using latex to create a pdf file. I don't want to merge these files
> each time somebody
> creates a new pdf, but I don't want to exclude them either, because it is
> nice to be able to go to any
> version without recreating the pdf.
> The behaviour I am interested in is the following:
> 1) pdfs are ignored for merging, if there is a conflict the pdf can be
> deleted, because neither of them is valid anyway. It can be recreated
> easily
> from the .tex after it has been merged.
> 2) pdfs are versioned, i.e. I can immediately go back to any version.
>
>
> Any ideas?
>

Some would say you shouldn't do that. But I do not see why apart the fact
that pdf should not be considered to be a source file, which still does not
explain me why you shouldn't do that !

I had the same sort of problem with generated proof obligation files when
working with formal method, where I had, for my workflow ,to be able to keep
them under revision control, because they take hours to be generated, and
because history was needed to automatically decide whose proof was to be
kept and whose proof was to be throw away.
I used at the time a hacked hgmerge script that always keep my version of
the files in case of conflict. It worked well for my own purpose.

 I guess nowadays you can simply add a merge-pattern configuration in your
.hgrc or .hg/hgrc looking like :
[merge-patterns]
**.pdf = internal:local

-Mathieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090624/afc5518a/attachment.htm