X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 18 Jul 2008 10:27:39 +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: <20080718082739.GF5675@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <487FAFD9.2030501@x-ray.at>
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 22:47, Reini Urban wrote:
> 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:"

Uhm... not quite.  While colons will work as normal parts of a filename
in the general case, it's still very hairy to differ between an incoming
POSIX and an incoming Win32 path in case of a path starting with X:

Cygwin 1.7 still isn't Win32 input path agnostic and can't be, because a
couple of internals also rely on this feature so far.  The result is
that, for the time being, paths starting with X:/ or X:\ are handled as
Win32 paths.

So, to treat c:/ as subdir c:, you have to prepend a ./ in 1.7.  I'm not
happy with this, but I think (and hope) it's a minor discomfort.


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/