This is the mail archive of the
mailing list for the Cygwin project.
- From: "Dan Kegel" <dank at kegel dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Mar 2008 14:15:58 -0700
- Subject: FAQ suggestion
The last company I worked for tried bundling Cygwin (with sources, natch)
as part of a product. Predictably (to those who have tried this),
this caused big problems because it conflicted with any Cygwin
installed on customers' machines.
Looking at the archives, I see at least a couple other people have
tried to do this, e.g.
but the Cygwin developers always reply with
"Don't do that. There can be only one instance of cygwin."
I'd like to see an FAQ entry about this, e.g.
--- snip --
Q. 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. Cygwin is not designed for this; the developers
official position is that there should be only one instance of
cygwin on any system, and that it should be updated
to the latest version constantly. So please don't try.
It will only bring you grief.
What, you're still here? Move on to the next question,
nothing to see here.
Oh, ok. If you want to do it anyway, one way to do it is to
change four places in the Cygwin source tree and
rebuild from scratch, then ship both source and binary of
Cygwin with your product. The four places are:
- change the updater to point to your own update server, or disable it
- change the name of the shared/common memory area
- change the location in the registry where Cygwin settings are kept
- rename the cygwin1.dll (such that all apps you build know the new name)
It's a daunting prospect. One can imagine a shell script that
automates producing such a modified version of Cygwin,
but nobody has written one yet.
--- snip ---
How's that look? Corrections welcome.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html