Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <12F176DD950ED411B68E0050DA14ED103387A4@jupiter.gunzphoto.com.au>
From: Neil Lunn <neillunn AT gunz DOT com DOT au>
To: cygwin AT cygwin DOT com
Subject: RE: problems with mulitple  cygwin installation
Date: Thu, 10 May 2001 10:34:41 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"


> -----Original Message-----
> From: Dario Alcocer [mailto:alcocer AT helixdigital DOT com]
> Sent: Thursday, May 10, 2001 10:15 AM
> To: cygwin AT cygwin DOT com
> Subject: Re: problems with mulitple cygwin installation
> 
> 
> >>>>> "Ralf" == Ralf Habacker <Ralf DOT Habacker AT saght DOT tessag DOT com> writes:
> 
>     Ralf> Hi for testing purpose I like to habe multiple cygwin
>     Ralf> installation and only the last installation works, because
>     Ralf> of the mount points are stored (and overwritten) in the
>     Ralf> registry.
> 
>     Ralf> Does anyone know a workaround for that ?
> 
> Of the top of my head, I'd try the following procedure:
> 
> 1. Pipe the output of the 'mount' command through awk or sed to
> generate a batch file that captures the mount points for the currently
> running installation instance.

Huh? Windows Registry! -- sheesh.
             ^^^^^^^^
There has already been a discussion on this list about regressing the cygwin
version (if you really really must do it).

Ultimately there is this. If you are concerned that your ported program
works with an older cygwin than a newer one, then THAT IS A PROBLEM. To
which end either cygwin and/or your program need to be fixed, depending on
who broke what.

If something breaks then it should break in a snapshot, so perhaps you
should look there. But I doubt your problem is with cygwin.

There is often a lot of work put into backward compatibilty, so maybe you
should consider using that.Freeze your versions of source, freeze your
release binaries, and test them on a current cygwin instead. I'd say that is
a far more practical solution to what you are suggesting.

Neil




__________________________________________________________________________
Please Note :
Only  the intended recipient is authorised to access or use this e-mail.  If
you are not the intended recipient,
please delete this e-mail and notify the sender immediately.   The contents
of this e-mail are the writer's 
opinion and are not necessarily endorsed by the Gunz Companies unless
expressly stated.

We use virus scanning software but exclude all liability for viruses or
similar in any attachment.



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple