> Our software products use different components, where many base components are used in different products. It is not necessary that all developpers compile these componentens themselves, that is, these components are distributed binary (as object files or libraries).
> To make the distribution of binaries easier, some developers started to include also object files and libraries of the common base components in the subversion repository.
> I know that subversion was not invented for that purpose, but from our experience it seems that it actually works.
> My questions:
> What kind of problems could occur if too many binaries are in the subversion archive?
Subversion handles binary files well. It's commonly used to store the
"golden master" files of software releases.
It sounds like you're using Subversion for dependency management,
too. This has some advantages:
- 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.
- Slower checkouts, updates, and merges due to working copy size
Also, you'll miss the features of language-specific dep-mgt tools, which
have a lot of sanity checks built in. A few examples: