Frederic Brehm wrote: > At 02:08 PM 7/21/2004, Jim.Hyslop wrote: > >OK, let's run through a use-case scenario: > > > >Scenario: Repository has a file named 'file'. User wants to > 'cvs add File'. > > > >CVSNT server, Windows client: 'add' command ignored > >CVSNT server, UNIX client: 'add' command fails: "File added > independently by > >second party" > > > >UNIX server, Windows client: add command ignored > >UNIX server, UNIX client: add and commit will succeed. > > > In your scenario, it appears to me that the only failure > comes with the > CVSNT server and UNIX client. Just because CVS does its job properly does not mean that there is no failure.
In this scenario, assuming a mixed-platform project, there are actually two distinct failures: one where CVS issues an error message; and another where the tool itself did not fail, but there was a violation of the larger configuration management picture. > So, the only problem comes when CVSNT is used as a server. > Therefore, use a UNIX server. No, there is also the problem when CVSNT is used as a server, and a UNIX user forgets, ignores or blatantly breaks the project rules around file names. > If you plan on sharing the same files between Windows and unix-like > systems, then you have to make sure your filenames are OK on > both systems. True, but if all else is equal, and you have a choice between a tool that allows you to break the rule, and a tool that enforces the project rule, isn't it much better to eliminate the human factor and choose the tool that can help enforce that rule? -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs