Re: Forcing DOS line endings on checkout/update

[Greg A. Woods]

[ On , August 1, 2001 at 16:13:55 (-0400), Laine Stump wrote: ]
> Subject: Re: Forcing DOS line endings on checkout/update
>
> Don't confuse the act of placing the CVS _repository_ on a
> shared/remote filesystem, then using :local: CVSROOT pointing at this
> NFS/SMB/whatever mounted directory to get at the files from multiple
> machines, with the act of checking out a _working directory_ onto a
> shared/remote filesystem. The former is a dangerous thing, and is what
> is warned against in all the documentation.
> 
> There is no similar warning against the latter, and as a matter of

"Wanna make a bet?"  :-)

If that's really true then that's a major failing because there really
should have been lots of warning given about this problem.  I know I
encountered it first in about 1994 when a colleague using pre-C/S CVS
was FTP'ing files back and forth to the Unix host (and running CVS on
the Unix host of course) and then accidentally made the mistake of
editing a bunch of the files on the Unix side.  They were dbase source
files and I don't think there was any problem with dbase reading them,
but editing them again on the M$ side caused unnecessary changes to
appear.  Once every such file was edited and saved again on the M$ side
all was well again, of course.

> fact it has often been said that this is just fine.

Yes, it's perfectly fine IFF all the hosts doing the sharing are of the
same type!  I do it all the time between Unix hosts, and in fact I've
done so ever since I started using C/S CVS (since that was the safest
way to use CVS remotely before C/S was possible too).

> For that matter,
> in many development environments, it is *required* (eg, when
> developers must, by corporate edict, keep their work directories on a
> server to facilitate easy backup).

Now look who's confusing things -- those are two entirely different
issues.  Storing files on a network filesystem does not imply sharing
CVS work directories between disparate platform types.  If the network
filesystem is transparent then it will not present a problem (and I
agree that storing working directories on a network file server is a
good idea!).  However just because you can share those directories
doesn't mean you should or must.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>