[racket-dev] A story of a package split

From: Tony Garnock-Jones (tonyg at ccs.neu.edu)
Date: Tue Aug 13 16:49:26 EDT 2013

On 08/13/2013 04:42 PM, Nick Shelley wrote:
> Can you elaborate on your intermediate form? I don't understand how git
> submodules prohibit or restrict submodule evolution. The only difference
> I see with the submodule approach is that it requires an extra commit to
> update the submodule versions (and subsequently a pull followed by a
> submodule update in other clones), whereas the makefile approach only
> requires a 'make update' in the umbrella clones. Is there something else
> I'm missing?

Perhaps you're right. Maybe my impression that git submodules are frozen 
is out-of-date. It has been a while since I used them. Perhaps they're 
first-class checkouts that can be manipulated independently of their... 
supermodule. If that's true, perhaps they're an OK way of specifying a 
versioned subrepo manifest.


Posted on the dev mailing list.