X-Spam-Check-By:	sourceware.org
Date:	Thu, 17 Aug 2006 14:09:23 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Cc:	Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: change in behavior of make from 3.80 to 3.81
Message-ID:	<20060817120923.GF20467@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com, Eli Zaretskii <eliz AT gnu DOT org>
References:	<6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816091525 DOT 0ab90af0 AT pop DOT nycap DOT rr DOT com> <20060816144110 DOT GX20467 AT calimero DOT vinschen DOT de> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816111421 DOT 0b446b60 AT pop DOT nycap DOT rr DOT com> <20060816155054 DOT GY20467 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0608161418370 DOT 9095 AT access1 DOT cims DOT nyu DOT edu> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816144036 DOT 09695af0 AT pop DOT nycap DOT rr DOT com> <Pine DOT GSO DOT 4 DOT 63 DOT 0608161543520 DOT 14156 AT access1 DOT cims DOT nyu DOT edu> <E1GDdoK-0002Ml-Re AT fencepost DOT gnu DOT org> <20060817093551 DOT GD20467 AT calimero DOT vinschen DOT de> <E1GDeSV-0004M2-M0 AT fencepost DOT gnu DOT org>
Mime-Version:	1.0
In-Reply-To:	<E1GDeSV-0004M2-M0@fencepost.gnu.org>
User-Agent:	Mutt/1.4.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 Aug 17 05:46, Eli Zaretskii wrote:
> > > Windows doesn't allow colons anywhere else in file names anyway.
> > 
> > That's not quite right.  Colons are also used in file names when the
> > file name denotes an alternative named stream on NTFS file systems.
> 
> Right, I forgot about this obscure feature.
> 
> However, this feature is not specific to Cygwin, so if support for
> such names is important (I suspect it isn't, but that's me), GNU Make
> should be modified to support them in all Windows ports; any solution
> that is good for other Windows ports will be good for Cygwin, and vice
> versa.  Do you agree?

Hmm, no, sorry.  I can't agree to "any solution that is good for other
Windows ports will be good for Cygwin".  This should be decided on a
case by case basis.

As for the NTFS streams, I mentioned them so that they are not left out
of the discussion.  Personally I agree with you that the support for such
names isn't overly important for make.  The reasin is this:

Colons are only a problem in the TARGETS and PREREQUISITES part of a
make rule, not in the COMMAND part.  But it only makes marginal sense to
use the ADS name for dependency checks, because a file has only one set
of timestamps for the whole file, not multiple timestamps, one per data
stream.  The availablilty on only one filesystem type restricts the
usefulness further.  So the ability to use ADS names in the COMMAND part
of a rule should be sufficient.


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/

- Raw text -