Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <432F2287.145DC1F2@dessent.net>
Date: Mon, 19 Sep 2005 13:41:43 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems
References: <0IN2009A5RCXL6 AT pmismtp01 DOT mcilink DOT com>    <Pine DOT GSO DOT 4 DOT 63 DOT 0509191358260 DOT 21521 AT slinky DOT cs DOT nyu DOT edu> <432F06FB DOT 7A5422B6 AT dessent DOT net>   <Pine DOT GSO DOT 4 DOT 63 DOT 0509191502560 DOT 21521 AT slinky DOT cs DOT nyu DOT edu> <432F122A DOT ADF69285 AT dessent DOT net>  <Pine DOT GSO DOT 4 DOT 63 DOT 0509191542200 DOT 21521 AT slinky DOT cs DOT nyu DOT edu> <432F1978 DOT DB503CF7 AT dessent DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0509191605530 DOT 21521 AT slinky DOT cs DOT nyu DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Igor Pechtchanski wrote:

> If either everything or nothing is encoded, that's only 2 possibilities.
> I originally thought that it would be enough to encode the differing
> characters, but therein lies madness, as you observed.

Right, I think that's what I was incorrectly thinking of.

> Not "nearly every file operation", only in case clashes are present...

Yes, but how do you know which version of the filename to use without
trying?  You don't know in advance whether you want the encoded version
or the plain version, so you'd have to try the one and if that fails try
the other.  And you'd need to do that for just about anything that
accesses a filename, like renaming, deleting, opening, etc.

> Isn't this what started this thread?  Explorer isn't the only Windows
> program that may inadvertently access (and get confused by) managed
> mounts.  Setup is a much more important one.
> 
> Besides, I can see the utility of, say, making /usr/src a managed mount
> (though only for non-official Cygwin packages, since the official ones had
> better have all their source files in the right case).

At the moment I see managed mounts as a relativly obscure feature that
should only be used when you have a stubborn package that's produced by
the kind of linux zealots who refuse to rename aux.c.  I certainly think
it should be only reserved for certain situations, and not used for all
of /usr/src.

It would be great if setup.exe could cope with managed mounts though. 
If someone sent a patch that would be super, but I don't personally
think it's something I'd spend time on.

> You must have missed the fact that nearly every source tarball contains a
> Makefile[.in]...  :-)  Besides, look in /usr/share/doc/...

My comment was referring to the scenario where you e.g. unpack a source
tarball (using cygwin tar) into a manged mount and then work on it with
a windows text editor.  In this case, it's annoying -- but something you
can still cope with -- that you have to open "%4Dakefile.in" instead of
"Makefile.in".

Brian

--
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/