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
On Jun 28 21:32, Reini Urban wrote:
Corinna Vinschen schrieb:
On Jun 21 20:24, Reini Urban wrote:
Yitzchak Scott-Thoennes schrieb:
On Tue, June 19, 2007 7:24 pm, Reini Urban wrote:
I want to it take over from Gerrit.
Thank you so much. If it were up to me, you'd get three gold stars.
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.
Corinna Vinschen schrieb:
On Jun 28 21:32, Reini Urban wrote:
Corinna Vinschen schrieb:
On Jun 21 20:24, Reini Urban wrote:
Yitzchak Scott-Thoennes schrieb:
On Tue, June 19, 2007 7:24 pm, Reini Urban wrote:
I want to it take over from Gerrit.
Thank you so much. If it were up to me, you'd
On Jul 2 19:06, Reini Urban wrote:
Corinna Vinschen schrieb:
- Your package pollutes the /usr/bin directory with two versions of
*almost* every tool in the perl package, foo, foo5.8.8, bar, bar5.8.8,
etc. The former 5.8.7 package only created a perl5.8.8 parallel to
the perl exe, but
Corinna Vinschen schrieb:
On Jul 2 19:06, Reini Urban wrote:
Corinna Vinschen schrieb:
- Your package pollutes the /usr/bin directory with two versions of
*almost* every tool in the perl package, foo, foo5.8.8, bar, bar5.8.8,
etc. The former 5.8.7 package only created a perl5.8.8 parallel
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
12 matches
Mail list logo
