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
Date: Fri, 28 May 2004 15:05:50 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: dll version collision
Message-ID: <20040528190550.GB5391@coe.bosbc.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <E164AD5F-B01F-11D8-BECE-000A95C4BF56 AT cipheroptics DOT com> <20040527212657 DOT GC2617 AT ata DOT cs DOT hun DOT edu DOT tr> <Pine DOT GSO DOT 4 DOT 58 DOT 0405271823590 DOT 25579 AT slinky DOT cs DOT nyu DOT edu> <7F99F48A-B0C5-11D8-BB92-000A95C4BF56 AT cipheroptics DOT com> <20040528171500 DOT GC26698 AT coe DOT bosbc DOT com> <DD50CCB2-B0CC-11D8-BB92-000A95C4BF56 AT cipheroptics DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DD50CCB2-B0CC-11D8-BB92-000A95C4BF56@cipheroptics.com>
User-Agent: Mutt/1.4.1i

On Fri, May 28, 2004 at 01:31:34PM -0400, Michael Hale wrote:
>On May 28, 2004, at 1:15 PM, Christopher Faylor wrote:
>>On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote:
>>>The ideas suggested here are definitely beyond my current ability.  I
>>>hope someone else who would like this done, and has the skill will take
>>>it up.
>>
>>If it is beyond your abilities then you shouldn't be considering this
>>option.  This is likely never to be an accepted way of using the cygwin
>>DLL.
>
>What is the correct way for someone to run multiple versions of cygwin
>on their machine then?  This seems like a very useful feature to me,
>since among other uses it would allow a new version to be tested along
>side an older but known version of cygwin.

You use the same technique as if you were testing another version of
linux.  Or you'd backup your system prior to updating cygwin.  It is not
likely that you could have two installations running on the same system
with no bleed between them.  Having two versions of cygwin working at
the same time is not a goal for the cygwin project.

cgf

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