Re: [tools-dev] OOo source split

2008-04-30 Thread Jan Holesovsky
Hi Mathias, On Wednesday 30 of April 2008, Mathias Bauer 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

Re: [tools-dev] OOo source split

2008-04-29 Thread Kay Ramme - Sun Germany - Hamburg
Caolan McNamara wrote: On Mon, 2008-04-28 at 20:25 +0200, Jan Holesovsky wrote: Another advantage is that it is also easy for the potential contributors to install just the -devel packages of the dependencies, and start with the development in the package where he/she wants to fix something

Re: [tools-dev] OOo source split

2008-04-28 Thread Jan Holesovsky
Hi Kay, Apparently I missed your mail - sorry for that :-( On Wednesday 09 April 2008 15:35, Kay Ramme - Sun Germany - Hamburg wrote: just wanted to suggest that re-using one or the other already existing structure for package re-organization would have some benefits. Possible candidates

Re: [tools-dev] OOo source split

2008-04-09 Thread Kay Ramme - Sun Germany - Hamburg
Hi Jan, just wanted to suggest that re-using one or the other already existing structure for package re-organization would have some benefits. Possible candidates IMHO are: -1- projects -2- modules You more or less already ruled out the modules approach, arguing along the line, that it

Re: [tools-dev] OOo source split

2007-10-16 Thread Jan Holesovsky
Hi Mathias, On Monday 15 October 2007 17:45, Mathias Bauer wrote: The advantage of one single 3rdparty package is that you either can use it as a make yourself happy with one click package or you don't use it at all and use each library as part of the already available 3rd party packages

Re: [tools-dev] OOo source split

2007-10-16 Thread Laurent Godard
Hi mathias The point is that people want to get rid of the whole process. That doesn't mean that we won't be able to build everything in one step but that shouldn't be the only way to build something that is part of the OOo code base. Thanks for your development laurent -- Laurent Godard

Re: [tools-dev] OOo source split

2007-10-15 Thread Martin Hollmichel
Jan Holesovsky wrote: Hi Mathias, On Friday 12 October 2007 20:18, Mathias Bauer wrote: just stumbled about that the report design extension is built during the regular build process, wouldn't it be better at all to create a source tarball include jfreereport and reportdesign modules. Where

Re: [tools-dev] OOo source split

2007-10-12 Thread Mathias Bauer
Martin Hollmichel schrieb: Hi, just stumbled about that the report design extension is built during the regular build process, wouldn't it be better at all to create a source tarball include jfreereport and reportdesign modules. Where we already achieved modularization in the sources we

Re: [tools-dev] OOo source split

2007-10-12 Thread Martin Hollmichel
Jan Holesovsky wrote: Eg. the spellchecker (hunspell) itself is in the lingucomponent which I propose to put to ooo-apps-extensions (and thus to ship it together with the application). The dictionaries for it are in ooo-libs-3rdparty/dictionaries - the distros have their own packages, but it

Re: [tools-dev] OOo source split

2007-10-11 Thread Rüdiger Timm
Mathias Bauer wrote: Rüdiger Timm wrote: Personally, I do not like spitting up sources at all. But that's my very personal opinion. Splitting up source definitely is a good idea. Maybe not for people building everything anyway but it would be a huge step ahead for the casual developer like

Re: [tools-dev] OOo source split

2007-10-11 Thread Caolan McNamara
On Thu, 2007-10-11 at 09:05 +0200, Rüdiger Timm wrote: My feeling is we should first do some work on our code base so that be really can benefit from a split. Perhaps a good case study of such a split is the modular X effort which broke the monolithic x.org build into separately buildable

Re: [tools-dev] OOo source split

2007-10-10 Thread Rüdiger Timm
Jan Holesovsky wrote: Hi Ruediger, I am sorry, I missed a part of the mail when I was answering previously :-( No problem. On Monday 08 October 2007 17:36, Rüdiger Timm wrote: This would tremendously decrease the learning curve for the new developers as well. Imagine someone who wants

Re: [tools-dev] OOo source split

2007-10-10 Thread Mathias Bauer
Rüdiger Timm wrote: Personally, I do not like spitting up sources at all. But that's my very personal opinion. Splitting up source definitely is a good idea. Maybe not for people building everything anyway but it would be a huge step ahead for the casual developer like volunteers, distro

[tools-dev] OOo source split

2007-10-08 Thread Jan Holesovsky
Hi, During the OOoCon, Petr had a presentation about the OOo package splitting. The most important part for a (Linux) package maintainer was to be able to build parts of OpenOffice.org separately; the thing is that with all the localizations, we are unable to get the build times under some 7

Re: [tools-dev] OOo source split

2007-10-08 Thread Jan Holesovsky
Hi Ruediger, On Monday 08 October 2007 17:36, Rüdiger Timm wrote: During the OOoCon, Petr had a presentation about the OOo package splitting. The most important part for a (Linux) package maintainer was to be able to build parts of OpenOffice.org separately; the thing is that with all