|
From: Rafael L. <ra...@ic...> - 2001-11-02 00:19:07
|
* Alan W. Irwin <ir...@be...> [2001-11-01 15:37]:
> We have had a discussion fairly recently on this list about when the GPL
> would be required, and I was summarizing my recollection of what Rafael
> said. But I may have it wrong, and the situation here is more complicated
> then the situation we were discussing before. However, *something* is
> linked to QT in order to run the pyqt GUI since I must set LD_LIBRARY_PATH
> to point to where I have libqt located in order for your example to work.
> Thus, I think some minimal amount of stuff will have to be GPLed, but I am
> not sure of exactly what. I don't have an axe to grind about GPL versus
> LGPL, but I do want to get this right so it does not come back to haunt
> us later.
>
> What do you think, Rafael? (I suspect you don't have time to comment much
> so what is the fundamental principle I should follow here to decide
> what needs to be GPLed taking into account that some of the "linking" is
> simply a user choice to read in the source from some of the xw??.py demos.)
You are right, I am too busy right now, but since you mentioned my name in
public, I feel myself in the obligation to reply :-)
To the best of my knowledge, the QT library is released under a dual
license, both GPL and QPL, at the users choice, I remember vaguely that the
QPL and the LGPL are claimed to be compatible (cannot remember where,
probably in the mailing list debian-legal). If it is true, this means
that any LGPL product can be linked against QPL. I may be wrong, though.
--
Rafael
|