From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Commercial use of cygwin
Date: Sun, 13 Dec 2020 16:43:31 +0000 [thread overview]
Message-ID: <DB7PR02MB399689A5C62E0BD3AB842A83E7C80@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <CA+kUOa=7AW3tD5EBtAjBYP8Rn7iEjdeqLC=jWhAowx57R=PPWA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2054 bytes --]
On 12/12/2020 18:44, Adam Dinwoodie wrote:
> On Sat, 12 Dec 2020 at 17:27, Hamish McIntyre-Bhatty wrote:
>> Do the points made here also apply to commercial but open-source use of
>> Cygwin?
>>
>> For extra context, I have an application with bundles parts of Cygwin
>> and libraries built against Cygwin. None of the source or binaries is
>> modified.
>>
>> I know I at least have to state which packages are included in the
>> bundle and provide links to the source for those, but I am not sure if
>> it is required that I eg provide a downloadable compressed folder with
>> complete source for everything.
>>
>> Can anyone give me some advice? The work everyone does for Cygwin is
>> valuable and I certainly don't intend to claim any of it is mine.
> The discussion in this thread so far, as best I can tell, amounts to
> "you need to comply with the license agreements in the packages you
> distribute". That is definitely the case for commercial open-source
> projects as much as it is for anything else.
>
> In my opinion, the safest way to make sure you're compliant is to
> provide all the source code for all the binaries you're distributing
> in the same way you make those binaries available; if you're shipping
> software on CD, ship the source code on the same CD; if you're
> shipping software by providing a download link, provide a download
> link nearby to the source code. In particular, it's not sufficient to
> merely point to the Cygwin website or even Cygwin mirrors, as those
> could disappear while you're still legally obliged to provide source
> code for at least anything with a GPL/LGPL/&c license.
>
> That all being said, I am not a lawyer, and I have no particular
> authority in the Cygwin project to assert what is and isn't
> permissible. Particularly for any commercial use, I would want
> professional legal advice on anything I wasn't confident about.
>
> HTH
>
> Adam
Thanks, that's to conclusion I came to for GPL'd code as well, just
wanted another opinion.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-12-13 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 8:42 Antonio Sidoti
2020-11-12 10:42 ` Marco Atzeri
2020-11-14 7:22 ` L A Walsh
2020-11-14 7:50 ` Marco Atzeri
2020-12-12 17:27 ` Hamish McIntyre-Bhatty
2020-12-12 18:44 ` Adam Dinwoodie
2020-12-13 16:43 ` Hamish McIntyre-Bhatty [this message]
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=DB7PR02MB399689A5C62E0BD3AB842A83E7C80@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.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).