Jan Holesovsky wrote: > Well, my _only_ motivation for the split are the build dependencies - so if > we > end up with 20 (sub)packages, or 15, I don't really care :-) Also, the names > are not that big deal for me (though I personally prefer better describing > names, and a kind of structure in them). What is the real problem from my > point of view is that currently you cannot take just one of the projects, and > (when you have the dependencies installed) self-containly build it. Also, if > you look at eg. framework, you see stuff that is essential for the OOo > functionality (desktop) as well as one that can be omitted (binfilter).
What level of granularity are you aiming at? I think that having separate packages for modules can work for many if we applied the necessary changes to scp2. Of course these changes will be more than some tweaking, it looks like a redesign to me. But there are some libraries/modules that are still very big and very intertwined with others. Making them available as separated packages with a reasobable size would require code changes also - and currently I don't see any activity going on to work on that. That's something I regret but OTOH I know that this is a resource problem. > But the approach of moving the modules between the projects is generally OK > for me. Just let's be careful not to end up in arguments like 'X: This > module needs to be built in project A, that way we'll have the smallest > dependencies. Y: Yes, but people in the project B know most about it.' :-) I don't understand who modules and projects relate here. Projects are completely irrelevant for modularization - we should use the modules as units for packages and try to bundle some smaller ones into one package so that the number does not become too high. But nobody wants a package "filter" or "utilities". > So - what can we do as the next step? Should I try to merge your and my list > to come up with the 'core' dependencies? Or could you, please? As long as the lists are project oriented and not module oriented we won't succeed. As alway, IMHO. :-) Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
