-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/2/2007 12:04 PM:
In the meantime, as long as the GPLv3 is not OSI certified (which
shouldn't take long), Red Hat will not enforce the GPLv2-only state of
Cygwin on the back of GPLv3 packages. So, tar 1.18 can
On Jul 2 15:09, Yaakov (Cygwin Ports) wrote:
Corinna Vinschen wrote:
There are no short-term plans to change the license of Cygwin, rather we
just wait until the OSI certifies the GPLv3 as open source license
according to the definitions. As Brian already noted, as soon as the
OSI
On 03 July 2007 08:09, Corinna Vinschen wrote:
And there I was trying to TITTLL the thread.
Oh well, anyone for hippos? ;-)
BTW, I just noticed the link to the OSI site is 404. It could be that it's
one of those sites that just don't work if you disable scripts and cookies,
but it's
On Jul 3 18:43, Dave Korn wrote:
BTW, I just noticed the link to the OSI site is 404. It could be that it's
one of those sites that just don't work if you disable scripts and cookies,
but it's more likely the link is just out-of-date.
Fixed.
Thanks for the hint,
Corinna
--
Corinna
On Jul 1 08:16, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
I'll try to get legal advice about Cygwin and the
GPLv3.
All this licensing stuff gives me headaches. I gave up trying to understand
it long ago.
Corinna, whenever you or someone else gets legal advice about this, I'd
appreciate it if a policy could be posted stating as clearly as possible
On Jul 2 10:40, Andrew Schulman wrote:
I'll try to get legal advice about Cygwin and the
GPLv3.
All this licensing stuff gives me headaches. I gave up trying to understand
it long ago.
Unfortunately the wording of the GPLv3 got rather less easy to
understand than the GPLv2. I can see
In the meantime, treat the http://cygwin.com/licensing.html page as
state of the art, especially the open source permission clause.
Thanks.
On Jul 2 11:28, Andrew Schulman wrote:
In the meantime, treat the http://cygwin.com/licensing.html page as
state of the art, especially the open source permission clause.
Thanks.
Ok, I got legal advice now.
Linking a GPLv3 application against a GPLv2-only library is not ok
because this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
There are no short-term plans to change the license of Cygwin, rather we
just wait until the OSI certifies the GPLv3 as open source license
according to the definitions. As Brian already noted, as soon as the
OSI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Red Hat will not enforce the GPLv2-only state of
Cygwin on the back of GPLv3 packages. So, tar 1.18 can stay in the
distro if Eric trusts Red Hat not to sue him.
I'll trust Red Hat much more than other companies that
On 02 July 2007 21:10, Yaakov (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
There are no short-term plans to change the license of Cygwin, rather we
just wait until the OSI certifies the GPLv3 as open source license
according to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/1/2007 8:16 AM:
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
Eric Blake wrote:
tar 1.18 was just released, and is one of the first GNU packages that
requires GPLv3 or later. Meanwhile, cygwin is explicit in requiring
exactly GPLv2. According to the GPLv3 FAQ, http://gplv3.fsf.org/dd3-faq,
it is NOT okay for a GPLv3 program to link against a
15 matches
Mail list logo
