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

How to avoid cluttering the svn repository with several versions of compiled files

From: Dymetman, Marc <Marc.Dymetman_at_xrce.xerox.com>
Date: Wed, 13 May 2009 13:26:42 +0200

Hi, I am a newbie to SVN, and have the following question:

 

Suppose that I am collaborating with several people on producing a book
using LaTeX.

I would like to use SVN not only for versioning the sources, but also I
would like to have in the repository an up-to-date version of the .pdf
(or .dvi, or .ps) compiled from these sources. The reason for that is
that, although the pdf is recoverable from the sources, it is convenient
for everybody to see the latest version without having to recompile the
sources.

I could compile the pdf in my working copy, and add it to the svn
repository, but then I would be cluttering the repository with many
versions of the pdf (for which SVN is probably not doing a good job at
incremental diffs).

 

Is there a way to tell SVN that the latest pdf file should *replace* the
previous one, that is, to force deletion of the previous revisions of
that file?

Of course I could save the pdf file somewhere else, not under version
control, but perhaps there is a way to do that inside svn?

(I guess my question would also make sense for binaries compiled from
programs, not only for Latex docs).

 

- Marc

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2235426

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-13 13:33:29 CEST

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.