Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 28 May 2004 15:05:50 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: dll version collision Message-ID: <20040528190550.GB5391@coe.bosbc.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040527212657.GC2617@ata.cs.hun.edu.tr> <7F99F48A-B0C5-11D8-BB92-000A95C4BF56@cipheroptics.com> <20040528171500.GC26698@coe.bosbc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/