From: "MrPmghost ." <pmghost4@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin licensing question
Date: Thu, 27 Feb 2020 10:48:00 -0000 [thread overview]
Message-ID: <CANH2EyXwKrGRq0fO=ioDY_h9N4=M+L2Mpg_RgRDmdSn9FTo+4Q@mail.gmail.com> (raw)
In-Reply-To: <CANH2EyVitsCrdz2LETbRORmp167ku4va4etU90y6YGTQ3nM2fg@mail.gmail.com>
Hi,
Thanks for all your feedback regarding this license subject. We will follow
your advice and ask a lawyer specialist in the matter.
Pierre
Le mer. 26 févr. 2020 à 17:37, MrPmghost . <pmghost4@gmail.com> a écrit :
> Hi,
>
>
>
> I am Pierre Meignen, software developer working for a belgium company.
>
> I have a question regarding cygwin and its use.
>
> Is it allowed/legal to integrate cygwin installer (2.11.1(0.329/5/3)) into
> the installer of an application that we plan to distribute commercially?
>
> I have checked the past cygwin posts but I did not see any clear answer to
> my question.
>
> I know how to handle source code in LGPL but I have difficulty to
> understand what I can do with cygwin (LGPL) but which also contains tools
> covered by the GNU GPL and so on.
>
>
>
> We have customized cygwin installer in order to install locally the
> necessary packages.
>
> Once in its execution, our application launches cygwin.bat and launch
> commands to upload embedded systems.
>
> We do not link towards cygwin.dll.
>
> We currently use the application internally but we plan to distribute it
> commerically in the future.
>
>
>
> Thanks in advance for your support/feedback,
>
> BR,
>
> Pierre Meignen
>
--
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
prev parent reply other threads:[~2020-02-27 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 16:37 MrPmghost .
2020-02-26 21:04 ` Brian Inglis
2020-02-26 21:38 ` William Deegan
2020-02-27 9:34 ` Corinna Vinschen
2020-02-27 10:48 ` MrPmghost . [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='CANH2EyXwKrGRq0fO=ioDY_h9N4=M+L2Mpg_RgRDmdSn9FTo+4Q@mail.gmail.com' \
--to=pmghost4@gmail.com \
--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).