public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: cygwin@cygwin.com
Subject: Re: [ANN] Cygwin-OpenSSH 8.2.2.2
Date: Thu, 27 Feb 2020 18:22:00 -0000	[thread overview]
Message-ID: <f5bd09zq4a4.fsf@ecclerig.inf.ed.ac.uk> (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:

> On Wed, Feb 26, 2020 at 11:47 PM ASSI wrote:
>
> You will perhaps want to read the Cygwin licensing terms
>> plus the licensing terms of each of the packages you distribute.
>>
>
> The relevant licenses are provided as links in the installer and referenced
> in the User's Guide.

What I believe everyone is being too polite to say explicitly is that
you have not conformed to Cygwin's license terms [1] yourself:

   What are the licensing terms?

   Most of the tools are covered by the GNU GPL, some are public domain,
   and others have a X11 style license. To cover the GNU GPL
   requirements, the basic rule is if you give out any binaries, you
   must also make the source available. For the full details, be sure to
   read the text of the GNU General Public License (GPL).

   The Cygwin™ API library found in the winsup subdirectory of the
   source code is covered by the GNU Lesser General Public License
   (LGPL) version 3 or later. For details of the requirements of LGPLv3,
   please read the GNU Lesser General Public License (LGPL).

I have tried pretty hard to find the Cygwin and OpenSSH sources in your
distro and cannot find them...

It seems likely that you're trying to do a good thing here, although in
general pointing people to the Cygwin site with instructions allows a
much better user experience than giving them a package which depends on
a 3rd party (you) for updates.  But you should play by the rules,
please.

ht

[1] https://cygwin.com/licensing.html
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
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:[~2020-02-27 18:22 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 [this message]
2020-02-27 18:52     ` Achim Gratz
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=f5bd09zq4a4.fsf@ecclerig.inf.ed.ac.uk \
    --to=ht@inf.ed.ac.uk \
    --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).