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
Date: Thu, 24 Aug 2000 15:06:04 -0400
Message-Id: <200008241906.PAA18573@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: aceschle AT thinkage DOT ca
CC: cygwin AT sources DOT redhat DOT com
In-reply-to: <20000824145741.A18153@mailhost.thinkage.ca> (message from Adam
	Schlegel on Thu, 24 Aug 2000 14:57:41 -0400)
Subject: Re: GUI setup
References:  <20000824145741 DOT A18153 AT mailhost DOT thinkage DOT ca>


Yeah, setup doesn't respect existing symlinks.  I think the easiest
way to deal with this is to use mount points instead, and teach setup
about the mount points (it can enumerate all the mount points at once,
and the built-in tar already has a mechanism to deal with a fixed list
of path conversions).

Why don't you just install cygwin on the other drive and be done with
it?

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com