On Mar 18, 2011, at 18:40:30, Colin Barrett wrote:
> IIRC, it's only a problem if they change, since Mercurial doesn't diff them. 
> But dSYM files don't ever change, they just sit there.

That depends on how you track them:

        dSYMs
                Adium.app.dSYM
                Adium.framework.dSYM
                etc.

        (updated every release, just before tagging)

or:

        dSYMs
                1.4
                        Adium.app.dSYM
                        Adium.framework.dSYM
                        etc.
                1.4.1
                        Adium.app.dSYM
                        Adium.framework.dSYM
                        etc.
                etc.

But that doesn't matter. The difference in repository size is nil: Either way, 
the contribution to repository size is the total size of each version's dSYMs 
times the number of versions. The only space difference is in the working copy, 
where the latter way will take up *even more* space once checked out.

The size of the data store will grow the same way—quickly—either way.

> I have literally dozens checked in to a particular project and its entire .hg 
> folder is 15MB. This includes source, assets, etc.

How big is each dSYM?

Adium's dSYMs, for a Release build of adium-1.4 [07d0037572c1], total up to 9.3 
MB, which is more than our current executable of Libpurple (6.8 MB).


Reply via email to