On Tue, Feb 28, 2012 at 4:47 AM, Stephen Butler <sbut...@elego.de> wrote:
> 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.
The bigger issue here is that you have to 'svnadmin dump/filter/load'
the entire repository for any maintenance like removing large objects
that are committed accidentally or something that should not be there
for legal reasons. This operation takes even more space and will
require more downtime as the repository grows. This problem becomes
even worse if you put multiple projects in a signal large repository.
> - Slower checkouts, updates, and merges due to working copy size
You can commit the libraries and executables only under tags (at a
slight break with convention) so they are only checked out by
externals when/where you specifically want them.
>> What better options for sharing versions of object fils are available?
> That depends on your programming language.
Which is unfortunate, because a lot of groups of developers use
multiple languages but want to share the same infrastructure. So
component-level subversion versioning may be the best you can do.
--
Les Mikesell
lesmikes...@gmail.com
