From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANN] Cygwin-OpenSSH 8.2.2.2
Date: Thu, 27 Feb 2020 18:52:00 -0000 [thread overview]
Message-ID: <87imjrj21y.fsf@Rainer.invalid> (raw)
In-Reply-To: <CANV9t=Tap+RQqSH2_po9qEVww0TNHgBiDcefc2ZioYU2yoG4PQ@mail.gmail.com> (Bill Stewart's message of "Thu, 27 Feb 2020 07:51:14 -0700")
Bill Stewart writes:
> The relevant licenses are provided as links in the installer and referenced
> in the User's Guide.
They are incomplete as they do not include the libraries you depend on.
But more to the point: since you include GPL components, a binary-only
distribution is not OK. The sources for at least the GPL licensed
utilities and libraries is missing. It's not enough to say what these
are and roughly where to get them and leave the users with figuring it
out for themselves, you are supposed to provide sources in the same way
as your binaries, for the exact version you used to create the binaries,
including any modifications to the build system or the sources
themselves.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
next prev parent reply other threads:[~2020-02-27 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 21:02 Bill Stewart
2020-02-27 6:47 ` ASSI
2020-02-27 14:51 ` Bill Stewart
2020-02-27 18:22 ` Henry S. Thompson
2020-02-27 18:52 ` Achim Gratz [this message]
2020-02-27 19:37 ` Bill Stewart
2020-02-27 22:31 ` Brian Inglis
2020-02-28 14:51 ` Bill Stewart
2020-02-28 17:45 ` Andrew Schulman via cygwin
2020-02-28 21:20 ` Andrey Repin
2020-03-01 11:53 ` Achim Gratz
2020-03-24 1:04 ` L A Walsh
2020-03-24 10:23 ` Adam Dinwoodie
2020-03-24 15:07 ` Bill Stewart
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=87imjrj21y.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).