X-Recipient:	archive-cygwin AT delorie DOT 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:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=E0/18IBwszlU373B5xfLq8fMiDvmIOgloVf/5BLhpJ/FJ5wmRSdXM
	nlJwLFFRLKIK+8gLy0AU2Ua2P6TFUwIkx62Ta8KmbVhBubkBfbHuqZPo7tYwK1u2
	34QFH4PID0lTTFftLJ14oIxpjLoTkTjihLCE7n+Sqnzsw0rgkCFRUA=
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:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=D/AoBRlC4tjP4UJUIZRi5dIe9yA=; b=ve06jVJdzYCROIFcTTuhcoLtkKMF
	KeBtASaKzm20lDpNp1GXqEunKaq5ha8wF9bDSLIgJmAblLBnEQm0QNq4gdPhUDQt
	r2rkAlexcvmi/dAFx08F2eF5vgw4afgzVTn8FvZn6OKwAcOOSzKHTSkch0kOeSZM
	hawp6XD5CQ+poww=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-104.2 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=lawyer, skilled, H*F:D*cygwin.com, customers
X-HELO:	mout.kundenserver.de
Date:	Fri, 29 Mar 2019 14:41:16 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	"Busch, Ciske" <c DOT busch AT mpdv DOT com>
Cc:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Re: Licence question regarding the delivery of Cygqin binaries
Message-ID:	<20190329134116.GJ4096@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	"Busch, Ciske" <c DOT busch AT mpdv DOT com>, "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
References:	<2bf31c739e144ea4b5e815ef44ed4522 AT mpdv DOT com>
MIME-Version:	1.0
In-Reply-To:	<2bf31c739e144ea4b5e815ef44ed4522@mpdv.com>
User-Agent:	Mutt/1.11.3 (2019-02-01)

--IgDDV5QArAYIxtdK
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 29 12:11, Busch, Ciske wrote:
> Hi,
>=20
> (I used this email as suggested (in a rather old) forum post from
> Corinna Vinschen. If this is not the right address I would be very
> thankful if you could point me to another address.)
>=20
> we have ported an older application from Linux to Windows and plan on
> using this in a commercial release. Due to the nature of the older
> application the Windows port uses tools from the Cygwin project which
> are called either from code or using shell scripts - we do not link
> either the Cygwin.dll nor any of the tools. You will find examples for
> scripts and the list of binaries used below. We do not plan on making
> our application available as open source.
>=20
> Our understanding regarding licensing is that as long as we do not
> link any part of the Cygwin distribution we are free to use them
> without implications for our own software.=20
>=20
> However we are not allowed to include the Cygwin binaries within the
> installer of our application - which is a problem for us as we need to
> have control over the versions our end users have installed.=20
>=20
> So my question is: is there a way for us to acquire a license which would=
 allow us to "bundle" the required Cygwin components with our software?

The Cygwin DLL itself is LGPLv3+.  The tools part of the Cygwin build
itself are GPLv3+.  All other Open Source tools not covered by the
Cygwin license retain their respective license.  Most of the licenses
require you, the vendor, to provide the source code of these tools under
the conditions of their respective license to your customers.  Some
licenses also require to add license information to your documentation.

There is no bundle licensing available!

Ideally you should add the sources of all Open Source software part of
your commercial offering to your software package, as well as adding the
OSS licensing information for all packages to your documentation.

However, you should really check your licensing situation with a lawyer
skilled in sofware licensing issues.  Naturally we can't give you any
viable advice in terms of licensing compliant behaviour here.


Hope that helps,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--IgDDV5QArAYIxtdK
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlyeIHsACgkQ9TYGna5E
T6CIOA//TTk4wHJ/SlhVdC0E8KVErXzqBPek5c2hgKE+ip1CarcuDwwvhnwDa46E
nKLhJRG7Q41GpBgzerrhm74MFGIrX4oe6DR/MH3liCG8VIF76mECdLWK76uRSidQ
R0eCpgz9i721UDzx6dk5UmhHSvQwwmISDhBcVKU/eEQHkc818ySU2IQ/f+Wk0PUC
Oi3hDSPLJUeOqO1YVDV6Y6nkvSlRnCSknMU/ffzYe454WYBq6nYPblc/56F4r8xc
6JEWRl6bftjwxzASXiA5nf9Q/BBvtpYUSsPkO4CByjDgH9KT9x4BDm3pAAfX6OG7
0JijdRVKwyCLrpAw5T4S23TnHxTn1J9ZTxb4OX9GfjJnaSlT0eBGGCwdkzZWGVTa
rv8wLElgtZGEbn2dkRPre3FHU7Uq7leObW92sWZhM3PBzfmpesreABMVn94OY8Bp
JhLggy1GvlQYSwWxXn0I2vma0YjtgYoRYU6j6vhyZEVVSsCGH16i0ZeOsoGG1sS3
/DDlpjVl0nTWWN4UhjOxRsoFLhSKtzlFcVhZFmyEPFafWtEYPXTKgmCC8MDhlOOa
H059SLynOWe5UyOf+QqCOufa1PdQ0gpQUjZpBjQmwt8Uy85k9UqukKO2CBnJHU4F
T7rSNu12/Zu9VSY0MrwtfwTeg0Y0yS16gp9fZViTLurDSkXW5/s=
=Occw
-----END PGP SIGNATURE-----

--IgDDV5QArAYIxtdK--

- Raw text -