On Mar 18, 2011, at 17:32:06, Colin Barrett wrote: > I've been checking them into Mercurial w/ my projects, right before tagging > the release. Seems to work well.
Checking several-MB binary files into a Mercurial repository is a good way to bloat it. We already have this problem with Libpurple; the biggest part of the .hg data store is the history of the Libpurple binary. This was the reason we had to split the conversion from our svn repo into two hg repoes (adium-old and adium), and why the adium-1.4 repo's data store has now already grown to 337 MB, more than 1/3 of which is Libpurple binaries.
