arsenetar
/
dupeguru
mirror of https://github.com/arsenetar/dupeguru.git
1
0
Fork 0
Code Releases Wiki Activity

Tranformed PyQt's license warning into a licensing note 

--HG--
rename : qt/WARNING => qt/ABOUT_LICENSE
This commit is contained in:
Virgil Dupras 2010-11-13 14:37:20 +01:00
parent 835050c337
commit 1b6e1369a0
2 changed files with 9 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
qt/ABOUT_LICENSE Normal file
View File

@ -0,0 +1,9 @@
PyQt is used in this UI package, and PyQt is GPL software. I used PyQt before going releasing my
source as BSD, so I have commercial license. When I released this software as BSD, I assumed that,
BSD being incompatible with GPL, anyone wanting to redistribute this code would need a commercial
license from PyQt. Therefore, I had a warning here telling people they needed a commercial license
to modify and redistribute the qt code.
But no! There are good news. I saw that PyQt has special permissions in its "GPL_EXCEPTION.TXT"
file, thus making everything nice and shiny. The license of this software package is compatible with
PyQt's GPL license. No problem here.

11
qt/WARNING
View File

@ -1,11 +0,0 @@
WARNING ABOUT THE HS LICENSE AND PyQt
Although Qt is now LGPL licensed, PyQt still is dual licensed. Until Nokia buys Riverbank and
releases PyQt as LGPL, users of this part of the code (The PyQt-based GUI code) have to use the
GPL version of PyQt, unless they possess a commercial license to it.
There is no problem to this AS LONG AS YOU DON'T REDISTRIBUTE HS LICENSED CODE. The GPL license, from the point of view of the user, is very permissive. You can do WHATEVER you want with the GPLed version of PyQt, as long as you don't redistribute any of the code, or code dependent on it. When you do, the code you distribute has to be GPL compliant. The HS license is NOT, I repeat, NOT compliant with the GPL.
So, what does it all mean? You have no restriction on the usage of the PyQt-dependent-HS-licensed code, but unless you possess a commercial PyQt license, Hardcoded Software (or anyone) cannot accept any contribution from you for this part of the code.
Note that this only affects the PyQt dependent code, and not any other part of HS licensed code (if it has "import PyQt4" in it, it's PyQt dependent code). For the rest of the code, the only restrictions that apply are the ones from the HS license.