Re: libgimp(ui), iibintl and (l)gpl problems
On Fri, Dec 03, 1999 at 06:28:42AM +0200, Tor Lillqvist <[EMAIL PROTECTED]> wrote: > That depends on exactly what source code you use to build libintl. The > "intl" directory from glibc is LGPL, but the same sources (more or > less) when distributed with gettext are GPL... Whew, I didn't know this! And which one do we distribute? I guess the one from gettext... > with glibc, but hacking together a Makefile is pretty trivial. For > Win32, I build the intl DLL from the LGPL sources. The problem is that we default to the gettext distribution. And people do not expect that their binary plug-in suddenly breaks the gpl because of such a hidden side-effect. (The real problem, of course, is the different licensing model). I'd at least warn the user when he uses configure --with-included-gettext -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: libgimp(ui), iibintl and (l)gpl problems
On 2 Dec, Marc Lehmann wrote: > However, if we solve this problem by *linking* libintl against > libgimpui we get another problem: linking against libintl > automatically puts libgimpui under the GPL. If you are using glibc2 then you've got not problem with lgpl, because its LGPL itself then... -- Servus, Daniel PGP signature
libgimp(ui), iibintl and (l)gpl problems
Marc Lehmann writes: > However, if we solve this problem by *linking* libintl against libgimpui > we get another problem: linking against libintl automatically puts > libgimpui under the GPL. That depends on exactly what source code you use to build libintl. The "intl" directory from glibc is LGPL, but the same sources (more or less) when distributed with gettext are GPL... I don't know if there are build procedures for building just the libintl part distributed with glibc, but hacking together a Makefile is pretty trivial. For Win32, I build the intl DLL from the LGPL sources. --tml
libgimp(ui), iibintl and (l)gpl problems
At the moment, libgimp&gimpui.so are not linked against libintl, which means they break on machines without gettext & friends in the libc. However, if we solve this problem by *linking* libintl against libgimpui we get another problem: linking against libintl automatically puts libgimpui under the GPL. I think the situation of "--with-included-gettext changes the license of libgimp to GPL" is not really acceptable. How are we supposed to solve this? Or should we just document this fact? -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
