Re: OpenOffice.org (LGPL) and hspell (GPL)
On Mon, Oct 04, 2004 at 10:10:41PM +0100, Chris Halls wrote: On Tue, 2004-09-21 at 11:33, Rene Engelhard wrote: Am Dienstag, 21. September 2004 12:28 schrieb Steve Langasek: Why not? If all of OOo is LGPL, then the license allows you to distribute under the terms of the GPL, so linking with another GPL library is ok. Hmm... Does this mean we would be changing the licensing of the packages from LGPL/SISL to GPL only? This may upset some users who are linking non-free modules to OOo at the moment. I'm thinking of the Finnish spellchecking and hyphenation module that Jarno Elonen packaged. FWIW, my take on this is as follows: - There does not appear to be any requirement to distribute LGPL code under the GPL just because it's linked to by other GPL code; c.f. glibc. - This suggests that the LGPL-GPL license conversion is actually taking place at runtime, rather than at the point of distribution. - If there exists a core codebase distributed under the LGPL, one or more modules using this codebase that are distributed under the GPL, and one or more modules using this codebase that are distributed under a GPL-incompatible license, we only run into problems if the incompatibly licensed modules depend on one another or are otherwise intended to be used together by default. - So as long as you don't upload a bizarre metapackage that pulls in Finnish and Hebrew spellcheck modules together :-), we should be ok. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: OpenOffice.org (LGPL) and hspell (GPL)
Hi, Josh Triplett wrote: I think the ideal solution would be to change hspell so that it can build outside of the OO.o source tree; as far as I know, it is OK to have some GPLed and some non-free plugins for the same LGPLed program, as long as they are not all distributed together. The hspell component uses the normal hspell lib (no problem here if we build from the hspell sourcepkg). But it also uses private headers and libraries from OpenOffice.org. The libraries are in openoffice.org-bin but the headers not in -dev. We could put all headers into -dev but I don't think this is a grandious idea wrt size and there probably is a reason why those headers don't appear in the SDK... Well, so it could only be built from hspell and not from us, so we can't fix that bug yet easily. Pity.. Grüße/Regards, René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 signature.asc Description: Digital signature
Re: OpenOffice.org (LGPL) and hspell (GPL)
Rene Engelhard wrote: Josh Triplett wrote: I think the ideal solution would be to change hspell so that it can build outside of the OO.o source tree; as far as I know, it is OK to have some GPLed and some non-free plugins for the same LGPLed program, as long as they are not all distributed together. The hspell component uses the normal hspell lib (no problem here if we build from the hspell sourcepkg). But it also uses private headers and libraries from OpenOffice.org. The libraries are in openoffice.org-bin but the headers not in -dev. We could put all headers into -dev but I don't think this is a grandious idea wrt size and there probably is a reason why those headers don't appear in the SDK... How many such headers does it use? If the interface is not expected to change often, hspell could do what programs which need linux kernel headers must do: include the headers it needs in the source package. Well, so it could only be built from hspell and not from us, so we can't fix that bug yet easily. Pity.. The license would permit it, and a GPLed OO.o wouldn't be *that* troublesome; the only major consequence would be that oo.o-java would need to go away. - Josh Triplett signature.asc Description: OpenPGP digital signature
Re: OpenOffice.org (LGPL) and hspell (GPL)
Chris Halls wrote: On Tue, 2004-09-21 at 11:33, Rene Engelhard wrote: Am Dienstag, 21. September 2004 12:28 schrieb Steve Langasek: Why not? If all of OOo is LGPL, then the license allows you to distribute under the terms of the GPL, so linking with another GPL library is ok. Hmm... Does this mean we would be changing the licensing of the packages from LGPL/SISL to GPL only? This may upset some users who are linking non-free modules to OOo at the moment. I'm thinking of the Finnish spellchecking and hyphenation module that Jarno Elonen packaged. This would arguably also affect the ability to package openoffice.org-java, since that links OO.o to a non-free JDK. I think the ideal solution would be to change hspell so that it can build outside of the OO.o source tree; as far as I know, it is OK to have some GPLed and some non-free plugins for the same LGPLed program, as long as they are not all distributed together. - Josh Triplett signature.asc Description: OpenPGP digital signature
Re: OpenOffice.org (LGPL) and hspell (GPL)
On Tue, 2004-09-21 at 11:33, Rene Engelhard wrote: Am Dienstag, 21. September 2004 12:28 schrieb Steve Langasek: Why not? If all of OOo is LGPL, then the license allows you to distribute under the terms of the GPL, so linking with another GPL library is ok. Hmm... Does this mean we would be changing the licensing of the packages from LGPL/SISL to GPL only? This may upset some users who are linking non-free modules to OOo at the moment. I'm thinking of the Finnish spellchecking and hyphenation module that Jarno Elonen packaged. Chris
Re: OpenOffice.org (LGPL) and hspell (GPL)
On Tue, 2004-09-21 at 11:28, Steve Langasek wrote: What are the advantages of hspell (which I've never heard of) over other spellchecking implementations already used by OOo, btw? The Hebrew language has a different form than English (or other latin based languages) and thus is better handled by different logic to infer what is a correct word and what is not. The standard method of prefix and infix used by (i|a)spell is not very efficient. I know that aspell is working on integrating word lists generated by hspell but it won't be as efficient and less able to provide useful corrections. Baruch
OpenOffice.org (LGPL) and hspell (GPL)
[ -legal: please let the CCs intact and CC: me, I am not subscribed ] Hi, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255451 contains a wish to include hspell support (upstream issue http://qa.openoffice.org/issues/show_bug.cgi?id=25832) into our OpenOffice.org packages and I want to do this starting with the upcoming 1.1.3 packages. The problem is that OpenOffice.org is LGPL/SISSL and hspell pure GPL so it could not be included in OpenOffice.orgs source and linking (in this case statically) against it is also not really ok... Well, how to build it then? Two possibilities: 1) we try to build this package from the hspell package. While this is probably the best solution this is the hardest ione since even when we get a openoffice.org-dev in 1.1.3, this stuff uses many private headers and libraries and so could not be easily built from hspell. Moreover, the buildsystem of this addon has to be fully reworked since it currently bases on 2) 2) build OOo, patch hspell in and built it against the built OpenOffice.org. This is the method the author of the add-on chooses and we could do this with some debian/rules magic too. However, this would mean a binary package of OOo would link with a GPLed lib (hspell). Is this allowed? Can I do that? Do I need to create an openoffice.org-hspell package or can I integrate this into the main ones? I hope I am clear.. Opinions? Suggestions? Can I do this or do I have to tag this bug wontfix since we cannot do it legally either way since this would be linking of a LGPLed app with a GPLed lib? Regards, René
Re: OpenOffice.org (LGPL) and hspell (GPL)
Hi, Am Dienstag, 21. September 2004 12:28 schrieb Steve Langasek: Why not? If all of OOo is LGPL, then the license allows you to distribute under the terms of the GPL, so linking with another GPL library is ok. Hmm... What are the advantages of hspell (which I've never heard of) over other spellchecking implementations already used by OOo, btw? OOo uses MySpell which does not really work for hebrew so hspell (which is exactly for hebrew) is to be used... Regards, René
Re: OpenOffice.org (LGPL) and hspell (GPL)
On Tue, Sep 21, 2004 at 12:01:52PM +0200, Rene Engelhard wrote: [ -legal: please let the CCs intact and CC: me, I am not subscribed ] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255451 contains a wish to include hspell support (upstream issue http://qa.openoffice.org/issues/show_bug.cgi?id=25832) into our OpenOffice.org packages and I want to do this starting with the upcoming 1.1.3 packages. The problem is that OpenOffice.org is LGPL/SISSL and hspell pure GPL so it could not be included in OpenOffice.orgs source and linking (in this case statically) against it is also not really ok... Why not? If all of OOo is LGPL, then the license allows you to distribute under the terms of the GPL, so linking with another GPL library is ok. What are the advantages of hspell (which I've never heard of) over other spellchecking implementations already used by OOo, btw? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
