> > We've just been bit in the butt again by Perforce on NT changing the case > of folders. I'm curious if our problems would go away if we switched to a > Unix based server. > > The situation is that we do development on Windows, Mac and Unix. A > majority of the development is done on Windows and Mac. About 6 months ago > we went through the db files on our server and converted all the paths in > our main code line to complete lower case paths. We also put a trigger in > place that checks all file adds to this code line and rejects them if the > paths contain anything other than lower case paths. > > Yesterday I integrated a branch into this main line of code that was > created before we converted all the paths to lower case. In our spot > testing Perforce did not change the paths on the existing files in main > when I integrated files containing mixed paths. Much to my chagrin,after I > submitted my integrate, Perforce had changed several of the folders in main > to mixed case. Now we've got to shut down the database again over a weekend > and reconvert all the paths costing development time and money. > > Now, on to the question.... > > If we went from an NT based Perforce server to a Unix one would any of my > problems be solved? Windows & Mac developers still could check in files > with mixed case paths, yes? Unix users would still be screwed when these > trees came down on their hard drives in shotgun fashion, yes? Is there > really a way around the problem other than converting our entire server to > lower case paths and running a trigger that looks at all Perforce > operations and rejects anything with a mixed case path?

We use perforce on unix, with clients on unix and NT, and all I can say is What problems? I think in the last 2.5 years there *may* have been two obscure cases where case was somehow a problem, I can't remember.

We don't have any triggers for case, or any special procedures to deal with case. We have about 340 users.

Our directory paths have mixed case in them, and it all seems to stay in order with no problems.

I remember the last time there was a discussion of case problems, the eventual consensus was that if you developed on case-insensitive and case-sensitive systems, then putting the server on the case-sensitive system was a win. The reasons were non-obvious though.

oh, and moving the server from case-insensitive to a case-sensitive system was deemed to be non-trival.

dave