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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=oj8UE3XRTlGvhiBttl/BeGvGdehTPQtWhfwCgIoGX5p3CBd9qEZvt
	2zkn3TKgWKIFyjYPVDUCiiz6UX9W4yJHVO97dJv1SanMPxRltJQ21x/1/7gxrZWY
	fU/aSxKzCHBSAAFG0rUJgVQU71sFuVw345LxaVJjrx+QZLE4wtRBEo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 27 Feb 2020 10:34:15 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin licensing question
Message-ID: <20200227093415.GA4045@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CANH2EyVitsCrdz2LETbRORmp167ku4va4etU90y6YGTQ3nM2fg AT mail DOT gmail DOT com> <3472932c-fd8f-fea6-21e8-01d8a06cd546 AT SystematicSw DOT ab DOT ca> <CAH_m2YJMeffvks2F4kHH5KH4FyCtVAF4T7+0BmrYAjr+imzJsg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="nljfjKcp9HDtPSOP"
Content-Disposition: inline
In-Reply-To: <CAH_m2YJMeffvks2F4kHH5KH4FyCtVAF4T7+0BmrYAjr+imzJsg@mail.gmail.com>

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

On Feb 26 16:37, William Deegan wrote:
> I'd also take a look at this:
> https://cygwin.com/licensing.html

https://cygwin.com/acronyms/#IANAL

I can't speak for any package in the distro apart from the setup tool
and the Cygwin package and its accompanying Cygwin-specific tools (the
"cygwin" package), but in terms of setup and the cygwin package, just
provide the sources of these packages together with your binaries.

If your way of distribution is a tweaked version of setup, you MUST
provide the tweaked sources to your customers per the GPL anyway.

If you provide all sources of all binaries you're delivering to your
customers, you're basically off the hook anyway.  Given that space and
bandwidth is not much of a burden these days, it's the easiest way to
comply with the idea of open source and their licenses.  The setup
tool is designed for source distribution anyway, so that's no problem
at all.

Apart from that, Brian is right.  You should really ask a lawyer who's
specialized in licensing.  Nobody here is qualified to give an answer
standing up in court.


Corinna


>=20
> On Wed, Feb 26, 2020 at 4:04 PM Brian Inglis wrote:
> > On 2020-02-26 09:37, MrPmghost . wrote:
> > > I am Pierre Meignen, software developer working for a belgium company.
> > > I have a question regarding cygwin and its use.
> > > Is it allowed/legal to integrate cygwin installer (2.11.1(0.329/5/3))
> > into
> > > the installer of an application that we plan to distribute commercial=
ly?
> > > I have checked the past cygwin posts but I did not see any clear answ=
er
> > to
> > > my question.
> > > I know how to handle source code in LGPL but I have difficulty to
> > > understand what I can do with cygwin (LGPL) but which also contains t=
ools
> > > covered by the GNU GPL and so on.
> > > We have customized cygwin installer in order to install locally the
> > > necessary packages.
> > > Once in its execution, our application launches cygwin.bat and launch
> > > commands to upload embedded systems.
> > > We do not link towards cygwin.dll.
> >                          cygwin1.dll
> >
> > > We currently use the application internally but we plan to distribute=
 it
> > > commerically in the future.
> > > Thanks in advance for your support/feedback,
> >
> > [Disclaimer: I am not any kind of lawyer or project lead just another
> > volunteer]
> >
> > Cygwin is not a formal organization and has no officers or lawyers, at =
best
> > volunteer project co-leads and maintainers with commit privileges to
> > primary
> > source repositories.
> >
> > Cygwin is an online project which has volunteers around the world
> > collaboratively maintaining a collection of packages archived and
> > distributed on
> > third party donated and supported domain names and infrastructure.
> >
> > Copyright and licence compliance is your responsibility if you download=
 any
> > binaries or sources. As you are based in Belgium in the EU you also hav=
e to
> > comply with Belgian and EU law which may have stricter copyright and
> > licensing
> > compliance requirements.
> >
> > Each package comes with its own licensing terms, including cygwin
> > (cygwin1.dll)
> > and setup (setup_x86{_64}.exe), usually under (case insensitively):
> >
> >         /usr/share/{,doc/}PACKAGE{,-doc}/*{COPY,LICEN}*
> > or
> >         /usr/share/doc/common-licenses
> >
> > You will have to provide your corporate lawyers with the licences for e=
ach
> > package you wish to include in your product.
> >
> > Your corporate lawyers will have to determine what responsibilities you
> > have
> > related to package licensing requirements, what you must do (e.g. publi=
sh
> > and
> > attribute all copyrights and licences in your product distribution and
> > documentation, distribute and provide online source archives, and submit
> > patches
> > upstream, etc.), and how you are limited by the licences in what you may
> > do with
> > each package.
> >
> > As so many packages are licensed under the [L]GPL2/3 or by the FSF if G=
NU
> > sourced, see https://www.fsf.org/licensing/ your corporate lawyers may
> > want to
> > work with the FSF Licensing and Compliance Team mailto:licensing AT fsf DOT org
> > or
> > their lawyers mailto:legal AT fsf DOT org as Cygwin has no lawyers.
> >
> > In general, you probably need to document, track, submit, and log
> > submission of
> > any modifications you make to any Cygwin package source code as patches=
 to
> > cygwin-apps AT cygwin DOT com, or upstream to the upstream package maintainer =
or
> > source
> > given in the package source archive, often shown in a .cygport file.
> >
> > Question for project leads - who maintains the maintainer copyright
> > assignments,
> > attributions, disclaimers, releases, etc. and where, or is that all also
> > only in
> > some mail archives?
> >
> > --
> > Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
> >
> > This email may be disturbing to some readers as it contains
> > too much technical detail. Reader discretion is advised.
> >
> > --
> > 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
> >
> >
>=20
> --
> 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

--=20
Corinna Vinschen
Cygwin Maintainer

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAl5XjRYACgkQ9TYGna5E
T6B81w//WSYfsqVunexNVBMDuT4sVPJ9BHnw10ga4/e7m0u4DrAr8aDCiIk67bzg
QPy5DsZscbXIDsjSEg1WCLveGxUoPfz3rlhLbX6D/ATQwgBDj5uhgO0CGraJlz1D
RceufeERMn1gfFVm5/S17fg+V26HeAI2TV/qdHlb9LXPx5qxZHVdExT9GxZnnnX6
mdPXKGPDCla8MJSypnctDmx9xhaUaqqwAXgjeTBZL+gYnC9/xd9wlf5ogc7XGnDO
Bdk1zRge61ea8v2Q3eYKVu+Q9gQ/3wN0KvkccDy2g8BsMzyG/XHbKGjAuJUjKuzl
Kqy26Q+E4+vHI+TVj7QDc6ka19ak4vO3g0PVxrE1xvv/XEyqmhPvmZFmT708II8y
1JTMAWl2P3QEm0yubPHAm8ENVYn21MFneIMo5freTLO3ncqakNSsfMks3Z7dtqTl
W2E9dD2qwOYwxbW0WkMRrBT4hJEJfwBqtUEpJ/mAXvUcv+fIKAQNOPQgTyz7dnIa
DsHcA9i43cYavZ00kGGh59uSOjKXol41E+y7DBZTWUK6LP3mkuFek/YI2EUGzgWy
MmePgDjZnM1Cr4A0Znhk9xE9wnmkXqqIn1KSIyAoW7Tthp8VN+zMLx/LQrme2q8I
7gT+AV/lCa5QZYXrBizI1XR+BmqDkBE0A8h6tTQPoPYfAwKqsac=
=HgV6
-----END PGP SIGNATURE-----

--nljfjKcp9HDtPSOP--