2012/1/13 Bob Archer <bob.arc...@amsi.com>:
>
> One issue we have is our legacy VB6 dll's that are built on every change. The
> dll's are put into source since most of our devs don't work on those binaries
> or can easily compile them. I have found that the bulk of our repo size is
> due to all these interim build versions. So, these are moved out of the
> primary source repository and put into a separate repo reference with
> externals. This repo can be replaced as it grows too big.
Yes, that is exactly the issue and I don't recall seeing any advice
about how to handle it or avoid the problem in the first place. I
mostly put off doing anything about it through the subversion 1.4->1.6
revisions while 'obliterate' sounded like a possibility. Now, that
doesn't look any closer to reality than it was years ago, so maybe
there should be some advice against getting into this situation
somewhere for people starting out.
> Now, source controlling external components is a judgement call. It might be
> better to just leave them in a public network folder and reference those
> locations in your source projects. Or, you can put them into source control,
> either the same repo or a separate one.
Our groups are very distributed and wouldn't all have access to a
common file share - and if they did it wouldn't be mapped the same for
everyone and wouldn't perform as well as using externals to pull the
copies in and update only on changes. We like the functionality, just
not the practical issue on the repository side.
--
Les Mikesell
lesmikes...@gmail.com
