Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Sun, 16 Jan 2005 10:14:50 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Multiple installations and 3PPs Message-ID: <20050116151450.GD16278@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <1105721403 DOT 28030 DOT 53 DOT camel AT localhost> <20050114171548 DOT GB6227 AT trixie DOT casa DOT cgf DOT cx> <1105726072 DOT 28030 DOT 78 DOT camel AT localhost> <41E9B859 DOT 8040102 AT isonews2 DOT com> <1105866703 DOT 28030 DOT 83 DOT camel AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1105866703.28030.83.camel@localhost> User-Agent: Mutt/1.4.1i On Sun, Jan 16, 2005 at 09:11:42AM +0000, Adrian Cox wrote: >I'm interested in failures that would still occur if the two cygwin >DLLs used different shared memory regions and registry keys. You can satisfy your curiousity. Remember this? http://sources.redhat.com/ml/cygwin/2005-01/msg00730.html I don't know if it has yet become obvious but this is not the first time that someone has suggested that they want to do this. I think trying to make multiple versions interact is a bad idea, so I'm not going to be doing any work in this regard. Since you don't seem to have engaged any of the other two cygwin developers, it seems like your only alternative is to do the work yourself. 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/