X-Spam-Check-By: sourceware.org
Message-ID: <51442.84.246.168.11.1160654571.squirrel@mail.morrison.mine.nu>
In-Reply-To: <20061012115416.GB8323@calimero.vinschen.de>
References: <452D2696 DOT 3060602 AT users DOT sourceforge DOT net>     <014c01c6ed5b$d6a1e9a0$a501a8c0 AT CAM DOT ARTIMI DOT COM>     <egjc38$teg$1 AT sea DOT gmane DOT org>     <20061012065523 DOT GP13105 AT calimero DOT vinschen DOT de>     <20061012111836 DOT GA29649 AT trixie DOT casa DOT cgf DOT cx>     <20061012115416 DOT GB8323 AT calimero DOT vinschen DOT de>
Date: Thu, 12 Oct 2006 13:02:51 +0100 (BST)
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
From: "John Morrison" <john AT morrison DOT mine DOT nu>
To: cygwin AT cygwin DOT com
Reply-To: john AT morrison DOT mine DOT nu
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, October 12, 2006 12:54 pm, Corinna Vinschen wrote:
>
> I think it is needed.  At least the base-files-mketc.sh postinstall
> script creates paths which point outside the Cygwin root, so it either
> needs to reference cygdrive paths, or use DOS paths.  Using cygdrives
> paths is preferable, IMHO.  Since the cygdrive path is not fixed, and
> can even differ between different users on the same machine, there must
> be a fixed method to reference these paths.
>
> Personally I'd rather not further clutter the root directory, which is
> why /proc seems to me to be a better place to point to the cygdrive
> paths in a constant fashion.  But that is only a mild opposition.  I'd
> also go along with /cygdrive.

I've changed the script (which I didn't write!) to use cygpath --sysdir
which outputs cygdrive paths.  I should be able to get a new release out
by the weekend, but I'll hold off until this discussion is decided. 
Personally I don't mind either an always existing /cygdrive or something
in /proc.  Only thing that would ask is; what would cygpath output?

J.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/