This is the mail archive of the
mailing list for the Cygwin project.
-----BEGIN PGP SIGNED MESSAGE-----
According to Brian Dessent on 6/30/2007 10:12 PM:
>> So, what is the consensus - am I allowed to upload tar 1.18, or is cygwin
>> forevermore stuck at tar 1.17 as the last GPLv2 release, because of the
>> fact that building an image of tar 1.18 linked against cygwin1.dll
>> constitutes a license violation?
> Remember that the Cygwin license includes an OSI exemption, so as long
> as GPLv3 is eventually OSI certified (as if...) it's fine on the Cygwin
> side. I don't know about the other direction though.
Thanks for the reminder about the exception clause. Since packaging tar
1.18 does not modify the sources to cygwin1.dll, I agree that the GPLv2
exception offered by cygwin is applicable here. I don't think GPLv3 will
have any problem achieving OSI exemption, so I went ahead and uploaded tar
Don't work too hard, make some time for fun as well!
Eric Blake email@example.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----