Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <41F0D6DB.8010107@gmx.ch>
Date: Fri, 21 Jan 2005 11:18:03 +0100
From: Roman <maillists AT gmx DOT ch>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Multiple installations and 3PPs
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hi,

I ran into the same problem as other did with different Cygwin version 
used by different 3PP's.
I do not need to have them run simulanously (at least not by now), but 
need to switch between them in a convenient way, if anyhow possible.

Christopher Faylor metioned in his mail the following:

>The cygwin developers know how to keep multiple versions of cygwin
>around for testing purposes so there really is no reason to add code
>just to accommodate people who are apparently using cygwin for
>commercial purposes without bothering to think too much about how they
>are installing it.



Since I am not a cygwin developer I am not too familiar with how Cygwin 
is installed and which registry entries matter.
Can anyone give hints or refer to cygwin documentation which entries are 
essential.

Or is the following approach a promising one:

1. Install the first Cygwin environement (e.g version 1.2)
2. Extend the installation path (e.g. C:\program\cygwin) and the 
registry entries with the key name "Cygnus Solutions" with a version 
extension (here -1-2).
3. Install the second Cygwin environement (e.g version 1.5.10)
4. Extend the installation path (e.g. C:\program\cygwin) and the 
registry entries with the key name "Cygnus Solutions" with a version 
extension. (here -1-5-10 )
5. Repeat step 3 and 4 for more Cygwin environements
6. Change the path name and the registry key name back to the original 
installation name for the version one wants to use. (manually or better 
write a script that doees the job)


Cheers

Roman

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