> Datum: Tue, 28 Feb 2012 11:47:43 +0100
> Von: Stephen Butler <sbut...@elego.de>
Thank you for the quick answer.
> But it also has disadvantages:
>
> - Runaway repository growth. Object files and .jar files don't compress
> as well as text. If you bust a hard limit for your repository disk space,
> your IT service provider might force you to pay a drastic penalty.
This is what I am afraid of; see also below ("representation-sharing")
> - Slower checkouts, updates, and merges due to working copy size
To prevent this, we can make a suitable seperation of binaries and sources in
the directory tree.
> Also, you'll miss the features of language-specific dep-mgt tools, which
> have a lot of sanity checks built in. A few examples:
>
> Java: Maven
> Python: virtualenv + pip
> Ruby: bundler + gem
We use C++.
> > How good does subversion make diffs of object code?
>
> By default, 'svn diff' skips binary files. You can customize it to use
> another
> program to display diffs for, say, "*.o" file.
This we do not need.
> There's a quick summary of binary-file handling here:
>
> http://svnbook.red-bean.com/en/1.7/svn.forcvs.binary-and-trans.html
>
> On the server side, Subversion stores files using a binary diff algorithm,
> and has a "representation-sharing" feature for avoiding redundant data
> storage.
Acutually this "representation-sharing" was my question. How good does it work
for compiled C++ code? How much does the repository typically grow?
> > What better options for sharing versions of object fils are available?
>
> That depends on your programming language.
C++
Helmut
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
