Change of CVS source directories
I realize this isn't something that would get done tomorrow, but what would be the chances of changing the CVS source directories to a naming scheme which would work on case-insensitive file systems? While that hasn't been an issue in the past, it is now with the growth of Darwin (MacOS X). Darwin supports HFS+, which is a case-preserving, but case-insensitive file system. The problem is that when you check out cvs, cvs tries to create cvs/cvs and cvs/CVS. On a case-insensitive file system, that won't work work. The problem could be resolved by simply renaming the cvs directory to cvssrc or some such. Now, I'm sure some Unix folks will argue that all file systems should be case sensitive. However, that's a moot point. HFS+ exists and is widely used. It is not going away and changing the file system is not an option. I realize that those who have servers that maintain a CVS image can probably resolve the problem by just renaming the directory on their own server, but since they frequently update from the main CVS distributions, it'd make life a lot easier if this could eventually be changed in the main distributions. Any thoughts? Wade ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
[EMAIL PROTECTED] wrote: > I realize this isn't something that would get done tomorrow, but what > would be the chances of changing the CVS source directories to a naming > scheme which would work on case-insensitive file systems? > > While that hasn't been an issue in the past, it is now with the growth > of Darwin (MacOS X). Darwin supports HFS+, which is a case-preserving, > but case-insensitive file system. whats a `mac'? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
[ On Wednesday, January 30, 2002 at 10:27:07 (-0600), [EMAIL PROTECTED] wrote: ] > Subject: Change of CVS source directories > > Now, I'm sure some Unix folks will argue that all file systems should > be case sensitive. However, that's a moot point. HFS+ exists and is > widely used. It is not going away and changing the file system is not > an option. HFS+ is not your only option in any scenario where use of an existing CVS repository containing case-conflicting files is likely to happen. Use a case sensitive filesystem for CVS (not just a case retentive one!). -- Greg A. Woods +1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
On Wednesday, January 30, 2002, at 01:19 PM, Greg A. Woods wrote: > HFS+ is not your only option in any scenario where use of an existing > CVS repository containing case-conflicting files is likely to happen. > > Use a case sensitive filesystem for CVS (not just a case retentive > one!). > I won't get into a legthy debate, but rather than making the CVS distribution friendly to all file systems, the answer is "get a different filesystem?" While I agree that there will be repositories that don't work on case-insensitive file systems, that's an issue for the maintainer of that repository. As more maintainers become aware that case-insensitive file systems are a real possibility, many will change their repositories to be file-system agnostic. While it's true the problem can be worked around, it just seems to me the CVS maintainers would want to be as compatible as possible, especially when the change is pretty easy. Wade ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
[EMAIL PROTECTED] wrote: > > On Wednesday, January 30, 2002, at 01:19 PM, Greg A. Woods wrote: > >> HFS+ is not your only option in any scenario where use of an existing >> CVS repository containing case-conflicting files is likely to happen. >> >> Use a case sensitive filesystem for CVS (not just a case retentive one!). >> > > I won't get into a legthy debate, but rather than making the CVS > distribution friendly to all file systems, the answer is "get a > different filesystem?" > > While I agree that there will be repositories that don't work on > case-insensitive file systems, that's an issue for the maintainer of > that repository. As more maintainers become aware that case-insensitive > file systems are a real possibility, many will change their repositories > to be file-system agnostic. > > While it's true the problem can be worked around, it just seems to me > the CVS maintainers would want to be as compatible as possible, > especially when the change is pretty easy. > > Wade maybe this will help you out: http://www.cvshome.org/docs/infomac.html why anyone would want to take a perfectly good filesystem under sans-BSD and munge it to "case-insensitive/case-preserving" is totally beyond me. you would have to go completely out of your way! .. -- there are many things in life you can be fashionably late to, but the MGM Grand Buffet is not one of them.. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
[EMAIL PROTECTED] writes: > > I realize this isn't something that would get done tomorrow, but what > would be the chances of changing the CVS source directories to a naming > scheme which would work on case-insensitive file systems? The current scheme works just fine on case-insensitive file systems. > The problem is that when you check out cvs, cvs tries to create cvs/cvs > and cvs/CVS. On a case-insensitive file system, that won't work work. > The problem could be resolved by simply renaming the cvs directory to > cvssrc or some such. Creating a directory named CVS on a case-insensitive file system is equivalent to creating a directory named CVS on a case-sensitive file system. As long as you store metadata in the file system, there is a potential for name clashes -- it is up to the users to avoid them. -Larry Jones ANY idiot can be famous. I figure I'm more the LEGENDARY type! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
[ On Wednesday, January 30, 2002 at 14:27:46 (-0600), [EMAIL PROTECTED] wrote: ] > Subject: Re: Change of CVS source directories > > I won't get into a legthy debate, but rather than making the CVS > distribution friendly to all file systems, the answer is "get a > different filesystem?" Absolutely! The problem is not with CVS, as Larry has so eloquently discussed, but with the repository you're trying to use. If you want to use a repository created from, and hosted on, a case-sensitive filesystem then you'd damn well better do so with your working directory on a case- sensitive filesystem, or face the consequenses of potential filename clashes! There's no magic here -- just pure plain common sense. -- Greg A. Woods +1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
On Wednesday, January 30, 2002, at 06:27 PM, Greg A. Woods wrote: > Absolutely! The problem is not with CVS, as Larry has so eloquently > discussed, but with the repository you're trying to use. If you want to > use a repository created from, and hosted on, a case-sensitive > filesystem then you'd damn well better do so with your working directory > on a case- sensitive filesystem, or face the consequenses of potential > filename clashes! > I never said there was a problem with CVS. However, the "master" distribution(s) of the CVS source code are setup for a case-sensitive file system. I was simply asking if the maintainers would be willing to change a directory name in order to be usable across all file systems. Apparently, the answer is no, so I'll leave it at that. Wade ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Change of CVS source directories
[EMAIL PROTECTED] writes: > > I never said there was a problem with CVS. > > However, the "master" distribution(s) of the CVS source code are setup > for a case-sensitive file system. I was simply asking if the > maintainers would be willing to change a directory name in order to be > usable across all file systems. Ah, I misunderstood your message, then. I thought you were asking for a change to CVS rather than a change to the CVS source repository. Now that I understand your question, I'm even more confused: There is no "cvs" directory in the CVS source repository, the top-level directory is "ccvs" (that may just be coincidence since it was originally Cyclic CVS, but I'm going to claim that it was done intentionally to avoid this problem). And, since it is a top-level directory, you can always just use checkout -d to rename it to whatever you want on your local system. -Larry Jones In my opinion, we don't devote nearly enough scientific research to finding a cure for jerks. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
