Hi, On Thu, Jul 29, 2010 at 10:56:53AM +0200, Thomas Schwinge wrote: > On Sat, Jul 24, 2010 at 04:19:46AM +0200, olafbuddenha...@gmx.net > wrote:
> > > > > > They have some very interesting translators, and these > > > > > > should be easily available. > > > You mean Git submodules? Yeah, that's an option worth considering. > > I'm a little undecided on submodules vs. monolithic repo. (I > > definitely dislike the idea of completely independant repos.) > > OK -- we do agree on that submodule one. (Isn't it nice?) ;-) Hey, I didn't say I agree; I only said it's worth considering... ;-) I'm actually not sure it's really worth the effort. But it's definitely something I could live with, *if* all the other issues are addressed. > My idea has always been to have such stuff in separate submodules, and > then have a overlying project (the top-level hurd.git one) that > contains a bunch of submodules (various translators; everything that's > intersting), can serve as sort of a tested distribution (because the > submodules are versioned), It would be more than a "testbed distribution" in my scenario. It would actually be the standard way of building the Hurd; of creating Debian packages etc. Only people who are interested in development of particular modules would ever want to build them standalone. > plus adding build machinery / cross-compilation support, etc. Just > added: > <http://www.bddebian.com:8888/~hurd-web/open_issues/populate_hurd_git_with_submodules_etc/> Do you actually have some kind of plan how to create an (autotools-based) build system, that allows both standalone compilation of individual modules, *and* building the whole thing in one go? (This would be useful for X.Org as well BTW.) -antrik-