Embraced language repos is a great path too. +1 for not having to tie automake into the respective language build systems. Ensuring that they all work together when Mesos is changing becomes a bit more difficult, but not worse than CI'ing builds of the respective "bindings" against HEAD (is "bindings" the proper term for the native / non-libmesos dependent / low-level API language support?).
However, is github.com/mesos a part of the ASF realm? Is it a common practice to do this? Niklas On 11 July 2014 08:37, Thomas Rampelberg <[email protected]> wrote: > > I guess one argument is that you have more fragmentation of the code > > (e.g every library has it's own copy of the protos) but I'm not sure > > that's a bad thing. > > I'd planned on having mesos be a submodule. That way, you'll get the > correct protos without any duplication. >
