From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8400 invoked by alias); 22 Apr 2008 15:51:44 -0000 Received: (qmail 8389 invoked by uid 22791); 22 Apr 2008 15:51:43 -0000 X-Spam-Check-By: sourceware.org Received: from out1.smtp.messagingengine.com (HELO out1.smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Apr 2008 15:51:26 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 6D52010155C for ; Tue, 22 Apr 2008 11:51:24 -0400 (EDT) Received: from web6.messagingengine.com ([10.202.2.215]) by compute1.internal (MEProxy); Tue, 22 Apr 2008 11:51:24 -0400 Received: by web6.messagingengine.com (Postfix, from userid 99) id CB3F5C687; Tue, 22 Apr 2008 11:51:23 -0400 (EDT) Message-Id: <1208879483.2504.1249265081@webmail.messagingengine.com> From: "Charles Wilson" To: cygwin-apps@cygwin.com Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Date: Tue, 22 Apr 2008 15:51:00 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00279.txt.bz2 Brian Dessent wrote: > the DLL already supports > parallel installs by the fact that it uses /etc/fstab. Only in very limited cases: (1) we're talking about cygwin-1.7.x (2) Either (a) only one of those parallel instances is in use at a time, including installed services, or (b) all of those parallel instances have exactly the same version of the DLL (3) Even so, doing this is not officially supported (the current dual-installation "support" vis-a-vis cygwin-1.5.x and cygwin-1.7.x is (a) temporary and (b) intended for package maintainers only, in order to prepare the cygwin-1.7 packages -- and package maintainers generally know what they are doing and what the pitfalls of a dual/multiple installation are. Right? You still have to worry about the shared memory region name, and its format which may vary with DLL version. Plus there still might be other stuff that prevents parallel cygwin installs from running simultaneously. And I don't think supporting simultaneous use of multiple cygwin installations is one of our goals, is it? -- Chuck