public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: cygwin@cygwin.com
Subject: Re: Multiple Cygwins/ Distributing Cygwin apps
Date: Mon, 03 Nov 2003 03:52:00 -0000	[thread overview]
Message-ID: <3FA5D0E9.7BB83BBF@dessent.net> (raw)
In-Reply-To: <bo4b1d$osa$1@sea.gmane.org>

John Moore wrote:

> For me, the inability to install two cygwins that are independent has
> already cost me a bunch of time. When I grumbled to a friend, his answer
> was "buy another machine for that application."

I have not tried this per se, but I don't see what's stopping you from
having as many Cygwins installed as you want.  Now, I'm not saying that
you could USE more than one at a time, due to the fact that only a
single Cygwin1.dll can be active at any given time -- and I wouldn't
expect this to change before the heat death of the universe.  But the
only thing that Cygwin touches outside of its install path is the mount
table in the registry, and this is easily removed/replaced with mount
and umount.

So, if I were doing this, I would install Cygwin #1 to \cygwin, then
"mount -m > mounts.txt ; umount -A", then install Cygwin #2 to \cygwin-b
or whatever, and so on.  To switch between them just unmount everything
and remount the other one.

Additionally, these vendors must have shipped you source to everything
compiled against Cygwin1.dll, or else they are in violation of the GPL. 
So, you should be able to recompile everything against the latest DLL,
and just use a single installation.  The exception is if they purchased
the Cygwin buy-out license from Redhat.

Brian

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

  parent reply	other threads:[~2003-11-03  3:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03  2:20 John Moore
2003-11-03  2:34 ` Gary R. Van Sickle
2003-11-03  2:51   ` Igor Pechtchanski
2003-11-03  3:12     ` Gary R. Van Sickle
2003-11-03  3:52 ` Brian Dessent [this message]
2003-11-03  6:27   ` John Moore
2003-11-03  8:24     ` Brian Dessent
2003-11-03 18:42       ` Multiple cygwins/ Distributing cygwin apps Christopher Faylor
2003-11-03 23:41         ` Igor Pechtchanski
2003-11-03 16:38 ` Christopher Faylor
2003-11-06 23:51 ` Multiple Cygwins/ Distributing Cygwin apps John Moore
2003-11-07 16:05   ` Multiple cygwins/ Distributing cygwin apps Christopher Faylor
2003-11-03 10:30 Multiple Cygwins/ Distributing Cygwin apps kevin.lawton
2003-11-03 17:46 Multiple cygwins/ Distributing cygwin apps kevin.lawton

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=3FA5D0E9.7BB83BBF@dessent.net \
    --to=brian@dessent.net \
    --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).