Re: cvs export end-of-line translation

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Maarten de Boer <address@hidden> writes:

> We do centralized tarball and zip-file generation for our project, and
> we use "cvs export" for this. The problem is that, since we run this on
> a GNU/Linux box, the files that get included in the zip all have
> unix-style end-of-lines. Is there a way to force "cvs export" to do
> end-of-line translation for a specific target? 

No.

You might use the GNU/Linux 'zip -l' command to do the *NIX end-of-line
character LF into the MSDOS convention CR LF translation for you... of
course, this assumes that all of the files are text files and can
survive this change.

> I could not find it in the manual, so I suppose not. Wouldn't this be
> a very useful, even logical, functionality? 

No, the cvs client is the one that knows how to do this transformation,
not the server. I suppose you could do your checkout using a DOS box and
have the GNU/Linux box mount that directory via samba to create the zip
files for you.

> I would say that this kind of use of cvs export is nothing out of the
> ordinary...

I do not agree as this kind of use violates the principle of least
astonishment.

> Right now, as a workaround, I use "flip" the change the end-of-lines
> based on filename wildcards, but this is not ideal. As another possible
> workaround, I'd prefer to ask the cvs server (without doing an
> additional checkout) which files are marked as binary. Is that possible?

Hmmm... yes, a 'cvs status' command will show 'Sticky Options:  -kb'
while other values for 'Sticky Options:' such as '(none)' would indicate
that the file is not binary.

You would need to post-process the output of the 'cvs status' command
to obtain your list of binary files.

        Good luck,
        -- Mark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/ismm3x41pRYZE/gRAnWUAKCuLvPHuvIEcxb3NkeXpLg1UREFQACeMzg1
gZFnFcmmlUf649GiQ2fjGmg=
=ZqQC
-----END PGP SIGNATURE-----