Re: moz-modular - splitting the tree

Enrico Weigelt wrote:

> the current code structure is really sad: one gigantic tree,
> no clear dependencies, a bunch of foreign packages.
> And the worst: doesn't get compiled.

What do you mean by "doesn't get compiled"? The mozilla tree is compiled 
(successfully) constantly by the tinderboxes at http://tinderbox.mozilla.org/

There are very good reasons for the large and monolithic appearance of the 
build tree. Don't knock it unless you have *specific* and *well-discussed* 
alternatives (which I'm happy to discuss, as time permits).

Modularization has real and substantial costs that are often not 
appreciated, especially when applied to mass-market end-user applications. 
See http://benjamin.smedbergs.us/blog/2005-07-29/the-testing-matrix/ for 
some of my thoughts on the subject.

--BDS