Message-ID: <487FAFD9.2030501@x-ray.at>
Date: Thu, 17 Jul 2008 22:47:21 +0200
From: Reini Urban <rurban@x-ray.at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: colons in Cygwin (was Re: make-3.81-3 (ITA??))
References: <487E8966.7020509@qualcomm.com> <20080717004748.GA30298@ednor.casa.cgf.cx> <487FAB2D.4000201@qualcomm.com>
In-Reply-To: <487FAB2D.4000201@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Rob Walker schrieb:
> I didn't mean for anyone (especially the package maintainer) to infer
> that make wasn't being actively supported.  My apologies for any
> misunderstanding.
> 
> I'm very interested in your opinions on colons in paths.  I'd prefer to
> hear directly what they are, to avoid any misunderstanding that might
> arise from me trying to glean them from the archives.
> 
> Questions I have in particular:
> 1. what are your thoughts on POSIX support for colons in paths?

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.

> 2. what are your thoughts on Cygwin's existing support for DOS paths?

Why should we? For mingw builds use MSYS, for cygwin use cygwin.
Don't mix what does not fit together.
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/

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