[Gpg4win-users-en] Switch from GPLv2 to GPLv3?

[Peter Rust]

Andre,

Thanks for the quick response!

> as it packages a combination of software which is partly
> licensed under the GPLv3 the GPLv3 applies to the combination

Cool, I didn't know that.

> Not sure about that and what you mean with spawn

This is regarding an existing (commercial) application that currently
downloads and installs its own updates via zip files. We're experimenting
with signing those update zip files on the server via "gpg --sign" and
verifying the signature on the client via "gpg --decrypt".

So the only piece of gpgp4win that I'm redistributing / including in our
application's client is the "gpg" executable and a few DLLs that it depends
on. I got these from the gpg4win project because it was the only place I
could find precompiled binaries, but I suppose the source code for these
binaries is all from the gpg project itself.

> My suggestion would be that you make the source installer and the source
package available

I assume you mean putting source installer on our website & allowing users
to download it from us -- that would work and we'll do it if necessary, but
it's a bit more work and IMO less useful to any interested parties than a
link to the official gpg/gpg4win source installer, which (from what I've
read) the GPLv3 allows but the GPLv2 doesn't.

But since the binary/DLLs I'm distributing is from the GnuPG GPLv3 sources,
I think I'm fine...

-- peter


On Thu, Oct 15, 2015 at 1:20 AM, Andre Heinecke <aheinecke at intevation.de>
wrote:

> Hi,
>
> 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
> source packages.
> http://files.gpg4win.org/gpg4win-src-2.2.6.exe
>
> 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 :-)
>
> Regards,
> Andre
>
>
> --
> 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
> _______________________________________________
> Gpg4win-users-en mailing list
> Gpg4win-users-en at wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/gpg4win-users-en
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wald.intevation.org/pipermail/gpg4win-users-en/attachments/20151015/ed7a189c/attachment.html>