Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <001101c152c0$90eaf400$4b0e4ea8@kepri.re.kr> From: "Jong B. Lee" To: References: <01e001c152ac$3e9d8e10$0200a8c0@lifelesswks> <3BC63169.9CCFCAD8@cportcorp.com> <021801c152b2$29276af0$0200a8c0@lifelesswks> <3BC63EBC.7070208@ece.gatech.edu> Subject: Re: Multiple cygwin installs: I have to do it, but how? Date: Fri, 12 Oct 2001 10:52:35 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id f9C1s4j02363 I'm still using the dinorsaur, B20. The registry is stored in a different place. Current cygwin : --Software--Cygnus Solusions--Cygwin B20 : --Software--Cygnus Solusions--CYGWIN.DLL I just installed both, and have no problem at all. No conflicts. JB Lee ----- Original Message ----- From: Charles Wilson To: Robert Collins Cc: Peter Buckley ; ; Sent: Friday, October 12, 2001 9:52 AM Subject: Re: Multiple cygwin installs: I have to do it, but how? > Back to earth: > > folks, we're talking about a product that is still using B19 for > gawsakes. ANY solution we come up with is NOT very likely to be adopted > by vendors that are FOUR YEARS behind. > > Honestly, given that we're dealing with a dinosaur, I think the best -- > and only -- solution is for users stuck with these archaic dists to > 1) push the vendors to update their products to work with modern > cygwins. To encourage them to develop packaging/installation methods > for their products that are compatible with "normal" packages in the > "net release" model. > 2) failing that, or in the meantime, these poor users should "swap > out" using batch files that update the registry and path settings > appropriate for different "sandboxes". This is ugly, hackish, and a > giant PITA -- but it's better than immense performance losses engendered > by other suggestions. > > That fact is, I'm not motivated to hack up the kernel in ugly ways, just > to help users of products from independent^Wincompetent software vendors > who refuse to modernize. Those ISVs deserve to lose customers. Harsh? > Maybe so -- but I'm a volunteer, not an employee. > > --Chuck > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > >