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:58:09 -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: <20040528195809.GA6108@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> <20040528190550 DOT GB5391 AT coe DOT bosbc DOT com> <20040528194634 DOT GA1325 AT ata DOT cs DOT hun DOT edu DOT tr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040528194634.GA1325@ata.cs.hun.edu.tr>
User-Agent: Mutt/1.4.1i

On Fri, May 28, 2004 at 09:46:34PM +0200, Baurjan Ismagulov wrote:
>On Fri, May 28, 2004 at 03:05:50PM -0400, Christopher Faylor wrote:
>>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.
>
>Well, with UML I have a reasonable environment to test most of things I
>have to deal with.  I would be happy to see the same for cygwin.

UML is not linux.  It is a mechanism for running linux in userspace.  If you
want to implement something like that for Windows, more power to you.  Or
you could just run VMware.

>>Having two versions of cygwin working at the same time is not a goal
>>for the cygwin project.
>
>Does this mean that if someone comes with a clean patch doing that, it
>would not be accepted?  Once it were there, it wouldn't require
>maintenance, any kind of user support can be explicitly disclaimed.
>What kind of problems do you expect?

I thought from this discussion that no one has the technical skills or
time necessary to use the facilities that are already part of cygwin.
Asking whether we would accept patches seems either rhetorical or at
least premature.

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/