X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 18 Jul 2008 10:34:05 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: colons in Cygwin (was Re: make-3.81-3 (ITA??))
Message-ID: <20080718083405.GG5675@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <487E8966 DOT 7020509 AT qualcomm DOT com> <20080717004748 DOT GA30298 AT ednor DOT casa DOT cgf DOT cx> <487FAB2D DOT 4000201 AT qualcomm DOT com> <487FAFD9 DOT 2030501 AT x-ray DOT at> <487FDBA9 DOT 2030909 AT qualcomm DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <487FDBA9.2030909@qualcomm.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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 Jul 17 16:54, Rob Walker wrote:
> Reini Urban wrote:
>> Colons in filenames are fine and will be supported with cygwin-1.7.
>> But c:/ it will not map to the root of some c drive, it will map to the
>> subdir "c:"
>> For now we had to use managed mounts for such names, soon we will be
>> able to see readable names.
>>   
>
> [RGW] This is interesting news to me.  This would break the planned GNU 
> make support for MSDOS paths under Cygwin, wouldn't it?  On which Windows 
> filesystems will this be useful?  In other words, where might one see a 
> directory named "c:" on a Windows box?

Cygwin is a POSIX emulation layer in the first place.  That's what we
are committed to in the first place.  Why would you want to use Win32
paths in a POSIX environment, except as parameter to native Win32 tools?
For dependency tracking in make there's no good reason to use the Win32
path.  You can just as well use the POSIX equivalent.  If you have to
convert between paths, there's the cygpath tool.

As for the directory called c:, you won't see it on most Windows
machines, given that Win32 doesn't allow it.  But you can see it on
POSIX machines and you can even see it on NTFS when using Microsoft's
SFU.  We're not explicitely talking about a dir called X:, but we're
talking about the general ability to use the colon as normal part of a
filename, as every POSIX system user usually can expect.  That leads
me elegantly back to my first sentence...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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