delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/03/18/23:48:08

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <a71bd89a0803182147y3ce38693gcac18c62072440a2@mail.gmail.com>
Date: Tue, 18 Mar 2008 21:47:28 -0700
From: "Dan Kegel" <dank AT kegel DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: FAQ suggestion
In-Reply-To: <20080319042138.GF22446@ednor.casa.cgf.cx>
MIME-Version: 1.0
References: <a71bd89a0803181415w18070c8u59c3091defcb1a5b AT mail DOT gmail DOT com> <20080318232317 DOT GA22446 AT ednor DOT casa DOT cgf DOT cx> <a71bd89a0803181715w3d267899vb01cddaa12810423 AT mail DOT gmail DOT com> <47E05D4D DOT 8000000 AT byu DOT net> <a71bd89a0803181737o4e15c0dcl67bb58f66a57afbc AT mail DOT gmail DOT com> <20080319040517 DOT GD22446 AT ednor DOT casa DOT cgf DOT cx> <a71bd89a0803182114p7edcffefh6288dbffd2614219 AT mail DOT gmail DOT com> <20080319042138 DOT GF22446 AT ednor DOT casa DOT cgf DOT cx>
X-Google-Sender-Auth: b75eda93fb44ff1a
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Christopher Faylor wrote:
>  I assume that they are either trying to 1) cheat, 2) bend the rules, 3)
>  not spend any time whatsoever worrying about the problem, or 4) become
>  annoyed because they have thought about it for thirty seconds and it
>  seems like we're purposely trying to punish them.

I have to think the question comes up frequently, else
it wouldn't elicit such a strong reaction.

>  But, yes, sure, a FAQ entry would not be a bad idea.

OK, I'm game:

--- snip ---

9. Deploying Cygwin

9.1  I want to bundle Cygwin with a product, and ship it to customer
sites.  How can I do this without conflicting with any Cygwin
installed by the user?

A.  Third party developers who wish to use Cygwin should check if
there is a version of cygwin installed and use the installed
version if it is newer, or conditionally upgrade if it is not.
(If you write a tool to make this easy, consider contributing
it to cygwin for others to use.)

9.2 Can I bundle Cygwin with my product for free?

A. Only if you comply with Cygwin's license very carefully.
If you choose to distribute cygwin1.dll, you must also
distribute the exact source code used to build that copy of cygwin1.dll.
If you ship applications that link with cygwin1.dll,
you must either provide those applications' source code under a
GPL-compatible license, *or* purchase a cygwin license from Red Hat.

9.3.  Can I install a private version of cygwin that doesn't conflict
with the system cygwin (in the same way that multiple versions
of Wine can coexist)?

A. The Cygwin maintainers will resist any suggestion to support
this, no matter how sensible it might sound to you, because
they feel strongly that the only supportable situation is
for everybody to use the same cygwin instance, and for it
to be as up to date as possible.

9.4. But doesn't that mean that if some application installs
an older Cygwin library than my system had, my application will break?

A. Yes.  If you run into such an application, uninstall it,
point the author to this FAQ, and try to get them to follow
the cygwin deployment rules.

--- snip ---

Is that getting closer?
- Dan

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019