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

Hello!

Dymetman, Marc schrieb:
> 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?

No. Due to the structure of the repository the content is stored on a
per-revision base and not on a per-file base. When using FSFS there will
*never* be peformed any modifications on already existing revision
files. This is a very important fact which will also be considered in
some backup szenarios.

Regarding deletion of old information look at several discussions about
a "svn obliterate" command which take place since several years. The
main reasons for such a command wouldn't be disk space savings but
legal requirements (accidentally checked in proprietary documents,
intellectual property, patents) or accidentally checked in *very big*
files.

> 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?

You could store your document in a revision property but I guess this
would be a really bad idea:

svn propset my:generated-files --revprop -r 123 `tar cf - file1.pdf \
  file2.pdf | uuencode'

Revision properties themselves are not versioned, so their content can
be changed afterwards.

I don't know if there are some space limitations on revision properties.

With best regards
Andreas Schweigstill

-- 
BITTE BEACHTEN SIE UNSERE NEUE TELEFONNUMMER!
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 53035-435, Fax: (+49) 431 53035-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2236193
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].