Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Tue, 21 Jan 2003 15:59:13 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: True case-sensitive filenames Message-ID: <20030121205913.GH17699@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <3E2D9E0E DOT 3050303 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Tue, Jan 21, 2003 at 03:42:54PM -0500, Gerald S. Williams wrote: >If you have a Unix/POSIX answer to that question, I'd really >like to know it. I don't get very far with package supporters >by telling them it's needed for a Windows port. I can sympathize. Is windows the only case-preserving/case-insensitive OS out there these days? Probably. And, cygwin was supposed to isolate everyone from Windows limitations as much as possible. Anyway, I would *really* like to see an implementation of the ideas expressed here. My only suggestion is "think generically" when you provide any changes. I don't know if the requirements for getting case sensitivity working on NT could be abstractable into something that would allow for future expansion into, oh, I don't know, nfs or something but I think it is worthwhile to consider not just adding a bunch of "ifs" to the code but going for something that could be "plugged in" somehow. Sorry if I'm getting too technical. :-) cgf