Re: best way to update large blobs in svn

Since the tarball is compressed (bz2) expecting Subversions diffing to save
you any space at all is probably a lost cause.

If you're going to expect many revisions of that tarball you're going to
need to consider at the least storing it without the compression - though
that will create it's own headaches in terms of working copy storage and
transmission (at least once) I expect.

--
Talden
On 7/3/07, Andreas Hasenack <andreas@mandriva.com.br> wrote:
>
> I have a situation where I will probably have to store in svn a large
> blob, like 230Mb. It's a tarball that only contains source code, but I
> need it stored as the tarball.
>
> I'm wondering if there is any best procedure about updating this tarball
> considering the amount of space that will be used.
>
> For example, say tarball-1.0.tar.bz2 is 230Mb and tarball-1.1.tar.bz2 is
> about the same size. It has a few differences, though (it's a new
> version). Usually, one would:
> - svn add tarball-1.1.tar.bz2
> - svn del tarball-1.0.tar.bz2
> - svn commit
>
> If I did a rename before to 1.1 and then updated the tarball, would it
> be better? Like:
> - svn rename tarball-1.0.tar.bz2 tarball-1.1.tar.bz2
> - cp ~/tarball-1.1.tar.bz2 .
> - svn commit
>
> Or even:
> - svn rename tarball-1.0.tar.bz2 tarball-1.1.tar.bz2
> - svn commit
> - cp ~/tarball-1.1.tar.bz2 .
> - svn commit
>
> I tried it here, but saw no noticeable difference in the repository
> size. The end result was sizeof(1.0)+sizeof(1.1) in all cases. Is there
> some other way or is that it?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>