Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Thu, 24 Aug 2000 15:06:04 -0400
Message-Id: <200008241906.PAA18573@envy.delorie.com>
From: DJ Delorie <dj@delorie.com>
To: aceschle@thinkage.ca
CC: cygwin@sources.redhat.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.A18153@mailhost.thinkage.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@sourceware.cygnus.com