public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <ebb9@byu.net>
To: cygwin-licensing@cygwin.com
Cc: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: GPLv3
Date: Mon, 02 Jul 2007 07:30:00 -0000	[thread overview]
Message-ID: <4687B75A.9020700@byu.net> (raw)
In-Reply-To: <468729AE.DFBAD955@dessent.net>

-----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 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
1.18.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----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

iD8DBQFGh7da84KuGfSFAYARAkBeAJkBBaUW2kxYXGCR7iSTzMKDtH78lgCg1lKf
94vXSl2zetTLNXk4BjAOtK8=
=GyNX
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-02  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02  7:29 GPLv3 Eric Blake
2007-07-02  7:29 ` GPLv3 Brian Dessent
2007-07-02  7:30   ` Eric Blake [this message]
2007-07-02  7:30     ` GPLv3 Eric Blake
     [not found]     ` <4687B75A.9020700-PGZyUNKar/Q@public.gmane.org>
     [not found]       ` <20070702073958.GY30973@calimero.vinschen.de>
     [not found]         ` <hg3i83tmt5uab1o9391mbtjivqo8p219gi@4ax.com>
     [not found]           ` <hg3i83tmt5uab1o9391mbtjivqo8p219gi-e09XROE/p8c@public.gmane.org>
     [not found]             ` <20070702151834.GC30973@calimero.vinschen.de>
     [not found]               ` <cc6i83djd9dg1132o063r4r4l94fhtl3b2@4ax.com>
     [not found]                 ` <20070702180442.GE30973@calimero.vinschen.de>
     [not found]                   ` <46895B87.3060908@users.sourceforge.net>
     [not found]                     ` <01c001c7bd00$8d50f050$2e08a8c0@CAM.ARTIMI.COM>
     [not found]                       ` <46898FC2.6020703@users.sourceforge.net>
2007-07-03  7:28                         ` GPLv3 Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4687B75A.9020700@byu.net \
    --to=ebb9@byu.net \
    --cc=cygwin-apps@cygwin.com \
    --cc=cygwin-licensing@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).