X-Spam-Check-By: sourceware.org
Message-ID: <4612C5E3.B972D9FB@dessent.net>
Date: Tue, 03 Apr 2007 14:23:47 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin snapshot and 'last-cache' file
References: <Pine DOT OSF DOT 4 DOT 21 DOT 0704032246400 DOT 7123-100000 AT ax0rm1 DOT roma1 DOT infn DOT it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Angelo Graziosi wrote:

> The file /etc/setup/last-cache contains path in DOS-like style:
> 
>    C:\cygwin\home\Angelo\Downloads\cygwin
> 
> When a script tries to retrive this information from 'last-cache' under
> the snapshot (for 1.7.0 release) there is the warning:
> 
>   cygwin warning:
>   MS-DOS style path detected: C:/cygwin/home/Angelo/Downloads/cygwin
>   Preferred POSIX equivalent is: /home/Angelo/Downloads/cygwin
>   CYGWIN environment variable option "nodosfilewarning" turns off this
>   warning.
>   Consult the user's guide for more details about POSIX paths:
>     http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
> 
> ... and I remember some discussion (MAKE-3.81 etc.) in which you were
> reluctanct in accepting the DOS-like paths.

I don't get it.  The script (what script?!?) should be updated to use
cygpath on the value read from the file, e.g. dldir=$(cygpath -f
/etc/setup/last-cache), just like any script that reads a key from the
registry or some program's .ini settings file or whatever.  The fact
that setup.exe happens to store its internal settings as a win32 path is
an internal detail, the file was never meant to be read by anything
else.  Besides, setup.exe is not a Cygwin app so storing its settings as
posix paths would just be extra hassle.

Brian

--
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/