On Thu, 13 Oct 2011 20:53:03 -0700, Kaz Kylheku <[email protected]> wrote: > If so, will the .tar.gz downloading via the CGIT web front recurse into > and pick up the submodule?
The author of CGIT informs me that CGIT just pulls out tarballs using git-archive, which only operates on what is in the tree. Submodules will come out empty. This is completely stupid; it means that users who don't want to (and should not) know anything about git cannot pull out a convenient snapshot of your code that will just unpack and build. This is just one among a number of indicators that git submodules are a dumb hack and a "second class object" that I will rather avoid using. I'm going with a tried and true approach: store the original tarballs of the third-party libs right inside the tree, and have my configure step unpack them and apply patches. (I can detect that quilt is available on the build machine, or else iterate over series files and call patch.) Having built and maintained a Linux distro, and migrated numerous stacks of numerous patches among revision hikes of numerous packages, this is very comfortable.
