From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23171 invoked by alias); 31 Jul 2008 15:41:15 -0000 Received: (qmail 23148 invoked by uid 22791); 31 Jul 2008 15:41:14 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 31 Jul 2008 15:40:57 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 7B5596D4354; Thu, 31 Jul 2008 17:41:04 +0200 (CEST) Date: Thu, 31 Jul 2008 15:41:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: New Cygwin 1.7.0-18 in release-2 Message-ID: <20080731154104.GN7319@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20080717155516.GC5675@calimero.vinschen.de> <4891623B.5060905@users.sourceforge.net> <20080731073904.GK22149@calimero.vinschen.de> <4891779D.5050406@users.sourceforge.net> <20080731114403.GA23628@calimero.vinschen.de> <4891D4B5.6060708@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4891D4B5.6060708@users.sourceforge.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-07/txt/msg00200.txt.bz2 On Jul 31 10:05, Yaakov (Cygwin Ports) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Corinna Vinschen wrote: > | Illegal? The only illegal chars are slash and backslash, even on > | case-insensitive mounts. Does it really occur often that you have two > | filenames in the same dir only differing by case? > > For Cygwin I understand that, but you mean to say that *setup* will be > able to install a file with a "*:<>|? (The : is the most common case, > usually within API docs, for obvious reasons.) Uh oh, you got me there. It shouldn't be ovberly complicated to tweak the untar code in setup to do the same special char conversion as Cygwin does, but, as usual, somebody has to do it. Maybe I'll look into that myself when I'm back in a couple of days. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat