Mathias Bauer wrote: > > And in addition to the aforementioned goals, maybe also optimizing > > the dependency graph for minimal cuts would be valuable (barring > > other criteria, like stable api)? > > Can you explain what "minimal cuts" means? > Hi Mathias,
sorry, was referring to this: http://en.wikipedia.org/wiki/Cut_(graph_theory) > I think that repository boundaries can help to avoid the erosion of code > separation. But OTOH if a code separation and its implementation as a > repository split turns out to be a bad choice, the split will be a PITA. > So we should not use repository splits to force people to work in a > certain way but rather find out what is the best or desired way to work > and support that by a repository structure that fits best to that. > Admittedly, constantly moving code across repository boundaries is a royal PITA. But I don't see a reason not to do that, after the split build setup has stabilized. Cheers, -- Thorsten
pgpM81naAAXC6.pgp
Description: PGP signature
