I think as long as Dominik supplies the source code he can release it
all under the GPL and do his own builds with his own plugins, Qt or not.
Now, If Dominik can NOT release his source code for his plugins then I
believe he must use the commercial Qt license.
No. He does not have to release it under the GPL if he is not
deriving/writing Qt code (he can do if he wants). plugins which do not
include Qt specific stuff do not have to be GPL
JB
A related distinction is that if you want to commit code to the vtk or
paraview repositories that has Qt code in it then you MUST have a
commercial Qt license otherwise you can submit a patch to the bug
reporter and someone that has a Qt Commercial license can commit your
patch to the cvs repository.
As always, I am NOT a lawyer, consult one if you feel you need more
clarification. This is not legal advice.. don't hold me liable for
anything, blah, blah blah..
Mike
On Nov 5, 2008, at 5:01 AM, John Biddiscombe wrote:
Dominik
Question is: do I need a commercial QT license. But I seem to get
the answer: no, as long as I do not use it myself and only rely on
PV whose source I reference.
I believe this is correct. If you are not writing any Qt related
code, then you are fine.
JB
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
--
John Biddiscombe, email:biddisco @ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
