From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
To: cygwin@cygwin.com
Subject: License compliance when shipping cygwin binaries
Date: Fri, 15 Jun 2018 10:56:00 -0000 [thread overview]
Message-ID: <721801b5-a98f-978a-35a9-f04c1dbfd95f@baur-itcs.de> (raw)
Hi List,
I would like to bundle and ship an executable found in Cygwin and the
DLLs it requires. The files in question are:
chgrp.exe
cyggcc_s-1.dll
cygiconv-2.dll
cygintl-8.dll
cygwin1.dll
For which of these files do I have to ship the source code to comply
with the license, and what's the easiest way to get hold of it myself?
(i.e. do I have to do a full cygwin install and select "source" on
$PACKAGE, then pick the source files from there, or is there a git repo
or similar that I could clone?)
The way I understand <https://cygwin.com/licensing.html>, I don't need
the source for cygwin1.dll (please correct me if I'm wrong). But what
about the other DLLs, and what about chgrp.exe itself?
I believe chgrp is under GPL, but I'm at loss whether there is a special
"cygwin chgrp" repo, or whether the regular chgrp source
(<http://git.savannah.gnu.org/gitweb/?p=coreutils.git>, I assume?) is
used, and how to fetch the source for exactly the binary I intend to ship.
Could anyone please enlighten me?
Kind Regards,
Stefan Baur
--
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
--
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
reply other threads:[~2018-06-14 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=721801b5-a98f-978a-35a9-f04c1dbfd95f@baur-itcs.de \
--to=x2go-ml-1@baur-itcs.de \
--cc=cygwin@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).