Re: Problems with large compressed binaries when converting from svn

From: Alex Riesen <raa.lkml@gmail.com>
Date: Jan 7, 2009, 23:55 UTC
Message-ID: <81b0412b0901071555t62c1da3ar2b2cfd14222b502e@mail.gmail.com>
In-Reply-To: <c09652430901060455l5179888ep3c51ff4e3dd5a6ef@mail.gmail.com>

2009/1/6 Øyvind Harboe <oyvind.harboe@zylin.com>:

Show 19 quoted lines

> I'm converting from svn and I've run into a
> problem with tar.gz and tar.bz2 compressed files.
>
> (This is a separate but only slightly related to previous post).
>
> In subversion we committed large tar.bz2/gz files. These files would
> change relatively rarely, but only very slightly.  The trouble with the tar.bz2
> format is that if the first byte changes, then the rest of the file will also
> be different. .zip does not have this problem, but .zip isn't a very friendly
> format for our purposes.
>
> Later on the tar.bz2/gz files started to change fairly often, but harddrives
> get bigger much more quickly than the .svn repository grows so we just
> kept doing things the same way rather than reeducate and reengineer
> the procedures.
>
> With .git we need to handle this differently somehow.
>
> Does git have some capability to store diffs of compressed files efficiently?

No, but you can unpack the tarballs and include the toolchains as submodules (aka subprojects) in the projects which need them.

See man page to git submodule, the user-manual.txt on "submodule" and gitmodules.txt (submodule configuration formats and conventions).