X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=JZBpa/NZT53iAQyR
	gq8IybS2r7ULsauqzU7ahnB+8Kj3Mdpm5jTuqH8qchpVOvKqTDslqBQs8Ib6JKKW
	GtiCewJ9hEfmuB/EBG183lir8iII44FJ1adYMxOISpJmfGmXoQdntvvEzb4R9jiB
	+ce2AS6ezgoEXa2aY7HgwI/pUeY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=aKrE4usdaLNU/5KqKHH9GX
	u2Pm8=; b=P+rEVUjkQ3vBIzhGSdzZpoFzjSmFwKhRRmtJsAZYdYl92HSkJSx4eo
	fLDykxxhiuQgj0mNz0wcqCrwPS0OZTnulzcoSKac8kBeJ6v0uPqW2OQ6gvky0W8g
	zjdf3GvzqS0SjgBrSQj0P3hsD9DFMlAzxo78G/QDrouMhxehn5HZs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=H*M:cygwin, H*Ad:U*yselkowitz, H*F:U*yselkowitz, H*MI:sk:6CBA673
X-HELO: mx1.redhat.com
Subject: Re: system lags and dysfunctional after cygwin update
To: cygwin@cygwin.com
References: <99f62d42-de9c-2209-85c4-42454ab9cf3c@gmail.com> <CE58DC48-A572-47AF-9EB7-61A124F83522@etr-usa.com> <d3f94b6d-b864-bb4a-d358-f3c685e690f0@gmail.com> <6CBA6730-6968-4CE8-ADEE-B18B05FB0A88@etr-usa.com>
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
Message-ID: <f290f3cc-ce78-ccf1-0cb3-cdecdc9d7d4b@cygwin.com>
Date: Fri, 13 May 2016 11:41:18 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <6CBA6730-6968-4CE8-ADEE-B18B05FB0A88@etr-usa.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

On 2016-05-13 10:38, Warren Young wrote:
> On May 13, 2016, at 8:02 AM, Ben Altman wrote:
>> I am not sure what is involved in packaging ksh with Cygwin
>> I was under the impression that if the licensing wasn't GNU it would be a
>> problem even though it is open source.
>
> Not exactly.  The license merely has to be *compatible* with the GPL as far
> as binary distribution goes, since the binaries distributed in the Cygwin
> package repo are linked to cygwin1.dll, which is GPL’d.

Please review: https://cygwin.com/licensing.html

Cygwin's license contains a linking exception for software licensed 
under terms which satisfy the Open Source Definition 
<https://opensource.org/osd>.  For our purposes, a good reference is 
<https://fedoraproject.org/wiki/Licensing:Main>.

> But after taking a peek at the AST license, it’s pretty clear it’s incompatible
> with the GPL.

True, but it is Open Source and therefore would be acceptable.

-- 
Yaakov

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

