public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANN] Cygwin-OpenSSH 8.2.2.2
Date: Thu, 27 Feb 2020 22:31:00 -0000	[thread overview]
Message-ID: <0853870f-74de-8ab5-835e-d97b310fcd91@SystematicSw.ab.ca> (raw)
In-Reply-To: <CANV9t=SyEJcGm3+--gWcvuuRQ0GOK206FaZ9PyoU5Xugh__r+A@mail.gmail.com>

On 2020-02-27 12:36, Bill Stewart wrote:
> On Thu, Feb 27, 2020 at 11:52 AM Achim Gratz wrote:
> 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.

> I misunderstood, since the source is already freely available from cygwin
> and I am not changing any of the binaries.
> 
> I can certainly include the source as a component in the installer for the
> next version.

No, you must backport all sources to the current and all previous versions and
redistribute, or at least make them visible and available on your site,
otherwise you are in breach of the licence and must withdraw all distributions -
see:

	https://www.fsf.org/licensing

and you may consult them for more accurate and complete information.

-- 
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

  reply	other threads:[~2020-02-27 22:31 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
2020-02-27 19:37       ` Bill Stewart
2020-02-27 22:31         ` Brian Inglis [this message]
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=0853870f-74de-8ab5-835e-d97b310fcd91@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).