[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Forcing DOS line endings on checkout/update

From: Greg A. Woods
Subject: RE: Forcing DOS line endings on checkout/update
Date: Wed, 1 Aug 2001 16:15:47 -0400 (EDT)

[ On Wednesday, August 1, 2001 at 09:40:54 (-0400), Alleman, Lowell wrote: ]
> Subject: RE: Forcing DOS line endings on checkout/update
> Fortunately, most of the stuff were are doing is binary (Oracle
> forms/reports, image files...).  So this whole text Unix/DOS line ending
> issue should be minimal, but I was trying to do it "right", and I really
> thought that this functionality would have already be included.

The problem is you're seeing the CVS world with tunnel vision.  Though
CVS itself works best on Unix, there are client versions that work on at
least three types of systems that are at logger-heads on this issue.
Building a solution for one of those three systems is not appropriate.
Building a solution for all three at the same time is either strictly
impossible, or will cause so much confusion as to be

The silly thing is that it's really not a CVS issue in the first place.
Most everyone who's been involved with multi-platform development (as I
have been for almost all of my career, even though only for a relatively
short period involving M$ systems, and quite some years ago now too),
it's best to keep your source repository in one standardised format
(even when that annoys some of the platform-specific developers
involved) and to use conversion tools to distribute platform specific
variants where necessar (which is *exactly* the same as using a compiler
to build a CPU specific binary from program source code!).  CVS is not a
build system.  Don't expect it to perform transformations on your source
files, no matter what they are inside.

I am kind a courious though -- just exactly what types of text files in
your environment must be converted?  I thought most systems that might
make use of such files (eg. database reports, documents, etc.) had more
than adequate facilities to deal with line {separ,termin}ator
differences on the producing system.

> I would much rather do this on the Linux side.

So, do it there!  You can always copy the files over the network to the
target systm after they've been mangled into the appropriate form for

                                                        Greg A. Woods

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]