You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Julian Foad <ju...@btopenworld.com> on 2003/09/02 22:46:02 UTC
Re: [Issue 1495] - Case sensitivity problem using file: on Windows
issues@subversion.tigris.org wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=1495
>
> ------- Additional Comments From kfogel@tigris.org 2003-09-01 11:22 PDT -------
> Yeah, that's annoying. Maybe the schema://host portion of a URL
> should be case-insensitively compared always, when checking for
> different repositories?
If it isn't already, it probably should be. But this issue is about the drive letter (which I believe is part of the "path" portion of the URL), as in "file:///c:/blah" versus "file:///C:/blah".
> Julian, if you have a Windows environment for testing, this might be
I don't have a Windows environment (except Wine, but I'm not very familiar with it and don't know if it should be trusted for this sort of testing).
> what you've been looking for. Adding you to CC list; just assign it
> to yourself and mark as started if you're interested.
Thanks. If I were to investigate it, I'd begin:
1. Check the case-sensitivity rules for URLs.
2. Check for any special cases for "file:" URLs.
3. Check for any official standard or consensus on handling drive letters in URLs, and whether the case-sensitivity of the drive letter should be different from that of the rest of the path.
I have a sort of feeling that case-sensitivity rules for the "path" portion of a URL might well be "It is the destination system's job to resolve a URL, including deciding whether it is case-sensitive." In that case we would have to have a-priori knowledge of the destination system. But - hey -
a. If the "file:" schema is being used, the destination system == this system.
b. If a drive letter is being used, the destination system is Windows, and at least the drive letter must be case-insensitive. (The rest of the path is probably case-insensitive too. Is that always the case on Windows?)
To resolve the issue as it is stated, it would probably be safe and sufficient just to make drive-letter comparisons case-insensitive. (That assumes that we really know that a drive letter is being mentioned, as opposed to a Unix path that happens to begin with a letter followed by a colon.) But it would be good to sort out the case-sensitivity of the rest of the path at the same time, if possible.
Sorry ... this isn't a particularly good one for me, though I suppose I could check that we are doing the right thing in terms of case-sensitivity at least in the absence of a drive letter.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1495] - Case sensitivity problem using file: on Windows
Posted by John Peacock <jp...@rowman.com>.
Jack Repenning wrote:
> Mmmm. OK. So would you say that Subversion can assume that any Windows
> file system is case-insensitive? It seems to me that some bozo
> somewhere is going to turn on POSIX, no matter how broken it is, and
> then SVN will be the one who looks bad for making the assumption.
No, it won't affect SVN, because you explicitely need to link to the POSIX
compatibility libraries in order to use those features. Show of hands: who
wants to test Subversion with system libraries that haven't been tested since
they were developed 6+ years ago??? It is not a matter of flipping some switch;
the entire Subversion build process under NT/W2K would need to change.
Search the list archives for CygWin, since they have already covered the ground
whether the POSIX feature for NTFS is worth using. It's a dead end. M$loth
only implemented it so they could claim POSIX.1 compatibility; even they aren't
dumb enough to actually _use_ it!
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1495] - Case sensitivity problem using file: on
Windows
Posted by Jack Repenning <jr...@collab.net>.
At 10:46 PM -0400 9/2/03, John Peacock wrote:
>
>Anyone requiring a case-sensitive filesystem should not use NTFS...
Mmmm. OK. So would you say that Subversion can assume that any
Windows file system is case-insensitive? It seems to me that some
bozo somewhere is going to turn on POSIX, no matter how broken it is,
and then SVN will be the one who looks bad for making the assumption.
--
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1495] - Case sensitivity problem using file: on Windows
Posted by John Peacock <jp...@rowman.com>.
Jack Repenning wrote:
> I've never done any of this, but I understand that recent Windows
> systems (?since NT4?) can enable "Posix file system mode," which
> includes case sensitivity. I also understand that this breaks lots of
> Windows programs, since they were bred and born case-insensitive. But I
> wonder if you can't create a non-boot drive that's POSIX, so long as
> you're happy with using only case-sensitive-capable tools on it. Like,
> say, Subversion.
I don't think you should recommend this. While it is true that M$loth
implemented enough of POSIX 1003.1-1990 (POSIX.1) to claim basic compatibility,
it is apparently very easy to accidently trash your file system. Only the POSIX
tools themselves (which have not been developed since they were first released
with NT4 Resource Tool Kit I believe) support directory entries with POSIX
enabled. None of the system libraries support POSIX, so anyone turning this on
would be unable to access the drive in any way except via the very primative
(and slow) POSIX tools.
The following M$loth KB entry is also quite scary:
http://support.microsoft.com/support/kb/articles/Q246/0/26.ASP
Anyone requiring a case-sensitive filesystem should not use NTFS...
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1495] - Case sensitivity problem using file: on
Windows
Posted by Jack Repenning <jr...@collab.net>.
At 11:46 PM +0100 9/2/03, Julian Foad wrote:
> b. If a drive letter is being used, the destination system is
>Windows, and at least the drive letter must be case-insensitive.
>(The rest of the path is probably case-insensitive too. Is that
>always the case on Windows?)
No.
I've never done any of this, but I understand that recent Windows
systems (?since NT4?) can enable "Posix file system mode," which
includes case sensitivity. I also understand that this breaks lots
of Windows programs, since they were bred and born case-insensitive.
But I wonder if you can't create a non-boot drive that's POSIX, so
long as you're happy with using only case-sensitive-capable tools on
it. Like, say, Subversion.
--
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org