Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3E2D79D2.1000307@yahoo.com>
Date: Tue, 21 Jan 2003 11:48:18 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: cygwin-developers AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Gerald S. Williams" <gsw AT agere DOT com>
CC: cygwin-developers AT cygwin DOT com
Subject: Re: True case-sensitive filenames
References: <GBEGLOMMCLDACBPKDIHFGEACDBAA DOT gsw AT agere DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Gerald S. Williams wrote:
> Christopher Faylor wrote:
> 
>>It just seemed like it was really prone to causing massive user
>>confusion for, IMO, little gain.
> 
> 
> I understand you're walking a fine line between offering
> true POSIX compatibility for Unix-types and getting beat
> up with questions from people on the Windows side of the
> house.
> 
> For me the gain is being able to port a project that uses
> case to distinguish C implementations from C++ wrappers,
> implementation from examples, etc. Currently, you can't
> even untar such a project very easily. I'd really like to
> be able to apply a simple patch file if needed (or better
> yet, get any Cygwin changes merged into the project). But
> this isn't practical if the project contains files that
> are unrecognizable/unavailable to Cygwin.
> 

IMNSHO, the problem is with the project that uses files that differ only 
in case.  It's not portable, and if the project wishes portability, then 
the practice must stop.  I urge you to raise an argument with the 
package maintainers accompanied with a patch.  Changing Cygwin to handle 
the problem isn't going to cause these problems to disappear as not all 
environments will support it.

Earnie.