[Gpg4win-users-en] Switch from GPLv2 to GPLv3?
aheinecke at intevation.de
Thu Oct 15 10:20:45 CEST 2015
On Wednesday 14 October 2015 11:28:06 Peter Rust wrote:
> Would you be open to moving gpg4win to the GPLv3 license?
The Gpg4win package is already GPLv3. Gpg4win itself (the buildscripts and
NSIS files) but as it packages a combination of software which is partly
licensed under the GPLv3 the GPLv3 applies to the combination.
> If I understand correctly, this would allow programs that spawn gpg4win to
> include a link to the gpg4win source code instead of requiring the
> redistribution of the 5.6mb source tarball (gpg itself uses GPLv3).
Not sure about that and what you mean with spawn. If you are distribution
Gpg4win as part of another software you have to comply with the License
restrictions of each component of Gpg4win.
E.g. You have to provide the installer scripts and the documentation sources
(which is in the 5.6mb source package) but also the sources of let's say GnuPG
because you are also distributing a binary version of GnuPG.
I'm not sure what you would gain though If we would change the Gpg4win
Installer scripts to GPLv3. They are already v2 or later so you can distribute
them under the terms of the GPLv3 and thus changing the license would imho
just add additional Restrictions.
We provide a source installer for this reason. That contains all the necessary
My suggestion would be that you make the source installer and the source
package available. This doesn't mean that you have to include it in your
binary installer. See the GPL for details :-)
Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: This is a digitally signed message part.
More information about the Gpg4win-users-en