Hi Mathias, On Tuesday 16 October 2007 10:12, Mathias Bauer wrote:
> As we are currently talking about splitting up the source I think it > makes most sense to have separate builds for each extension. Again I am a bit afraid of too fine granularity in the case 1 extension = one tarball. But we can think of having ooo-extensions-writer, ooo-extensions-calc, ooo-extensions-core (crashreporter, etc.), ooo-extensions-base, what do you think? Maybe even rename ooo-filters to ooo-extensions-filters? > So there > would be a package/tarball containing the jfreereport binaries and the > reportdesign sources. At least that's as I understood Martin and thus my > "+1". If he was aiming for something else of course that would turn into > a "-1". But I hope that I understood him right. > > > Either way, from my point of view it is plain 3rd party stuff, so I'd > > like to let it in ooo-libs-3rdparty. To avoid reportdesign intergrowth > > with Base, maybe ooo-apps-extensions would be the better option for > > reportdesign, what do you think? > > I think 3rd party stuff used in extensions should be separated from 3rd > party stuff used for the "core" code base. I would even like to keep > java libs separated from C(++) libs. Right, that might make sense. So instead of ooo-libs-3rdparty, we could have ooo-libs-3rdparty-c++, ooo-libs-3rdparty-java and ooo-libs-3rdparty-extensions. That would be OK for me :-) Regards, Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
