bug-cvs
[Top][All Lists]
Advanced

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

Re: Build CVS (TRUNK) failed.


From: Derek Robert Price
Subject: Re: Build CVS (TRUNK) failed.
Date: Sun, 29 Feb 2004 18:58:35 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1

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

Dennis Jones wrote:

>I'm not at all familiar with the CVS source code, but from a cursory
look, I
>don't see anything in those functions that is *nix-specific.  They look
>generic enough that they ought to compile cleanly in Windows.  If you would
>like to send me a modified set of files (with the appropriate .MAK file), I
>would be happy to do a test build for you and send you the results.


Actually, it's not the compiling I'm worried about.  It was the command
line quoting.  The quoting is currently aimed at getting arguments whole
past a Bourne shell parser.  What is going to happen when the same
command lines are passed to command.com?  Is back-slash the escape
character AND the directory separator?  Characters within single quotes,
including the single quote, cannot be escaped for Bourne shell.  Is this
true on Windows?

If someone could rewrite the quoting functions with command.com or
whatever it is that run_exec() in windows-NT/run.c uses in mind, it
would be greatly appreciated.

Derek

- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAQnyrLD1OTBfyMaQRAnl8AKCgeNAVuK+M9FcWtYn3QeqV4X6D3ACcCDmd
CwzTelGuc8wemx3xEF5me8A=
=8+6n
-----END PGP SIGNATURE-----






reply via email to

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