Jan Holesovsky wrote:
Hi Martin,
On Friday 12 October 2007 12:37, Martin Hollmichel 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 still must be possible to build with the internal ones.
I'd prefer to treat the dictionaries as an own package and not to bundle
them in a "super-source-package" ooo-libs-3rdparty package again. If we
have meaningful smallest possible packages we should go with them.
Yes, this is very tricky :-( For every module from ooo-libs-3rdparty we could
have a single package, but I'm afraid it would make the granularity too fine.
My vision is that on modern Linux distros, you won't need ooo-libs-3rdparty at
all, because you will have all the packages in the distro already, and you'll
be able to install them from there (most probably with the corresponding
-devel packages). But for the Win32 builders, searching for the dependencies
could be too expensive - that's why I propose the 'super-source-package' ;-)
Of course, we can go the way of ooo-3rdparty-dictionaries, ooo-3rdparty-epm,
ooo-3rdparty-hsqldb, etc. but I'm not sure if it helps in the end...
Keep in mind that the current situation is that some 3rdparty stuff
checked into OOo is either/both:
- accompanied by patch files to adapt to OOo requirements,
- required by OOo in specific versions.
So, in general, without cleanup, replacing 3rdparty stuff checked into
OOo with 3rdparty stuff available in the environment is just not working.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
