RE: Forcing DOS line endings on checkout/update

[Greg A. Woods]

[ On Wednesday, August 1, 2001 at 11:45:51 (-0400), Frederic Brehm wrote: ]
> Subject: RE: Forcing DOS line endings on checkout/update
>
> It seems like the request in the original message
>       http://mail.gnu.org/pipermail/info-cvs/2001-July/018162.html
> has been forgotten somewhere in this thread.

No, I don't think it has at all.  The answer is "no", and the reason is
that you should never share working directories between platforms with
incompatible line {separ,termin}ators, and explicitly trying to get
DOS-format files directly from a Unix CVS client is implicitly doing
just that.

> I think that Mr. Alleman wants to keep a checked-out copy as described in
>       http://www.gnu.org/manual/cvs-1.9/html_mono/cvs.html#SEC146
> but with an additional wrinkle: DOS line endings on some files.

Then Mr. Alleman should learn to use a build system (eg. "make" with
appropriate makefiles), and appropriate tools to do his conversions as
part of his build (eg. unix2dos).

What's so hard about:

        cvs export -r $NEWREL -kv -d $TMPEXPORT
        cd $TMPEXPORT
        make && make install

(where the final "make install" puts the converted files into a shared
directory)

There are an almost infinite number of ways to solve problems like this
once you get out of the mindset that the CVS manual explicitly cautions
you not to get into in the first place:

    CVS is not a build system.
    CVS is not a substitute for management.
    CVS is not a substitute for developer communication.
    CVS does not have change control
    CVS is not an automated testing program
    CVS does not have a builtin process model

all but maybe one of those apply in this case.

-- 
                                                        Greg A. Woods

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