Date: Wed, 30 Aug 2000 20:02:49 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Magnus DOT Lewis-Smith AT pace DOT co DOT uk
Message-Id: <2110-Wed30Aug2000200249+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC: "djgpp AT delorie DOT com"
	<44632C76B97BD211AF6B00805FADCAB2063331EF AT exchange DOT saltaire DOT pace DOT co DOT uk>
	(message from Magnus Lewis-Smith on Wed, 30 Aug 2000 15:50:04 +0100)
Subject: Re: DJGPP perl port vs ActivePerl line length
References:  <44632C76B97BD211AF6B00805FADCAB2063331EF AT exchange DOT saltaire DOT pace DOT co DOT uk>
Reply-To: djgpp AT delorie DOT com

> From: Magnus Lewis-Smith <Magnus DOT Lewis-Smith AT pace DOT co DOT uk>
> Date: Wed, 30 Aug 2000 15:50:04 +0100
> 
> In the script I am using $command is defined as
> 
>     my $command = "cvs -fQq -d $repos co -r $tag $1";
> 
> where the CVS executable was installed as part of the WinCVS
> distribution.

If this is a native Windows application, I understand why the command
line is truncated at 126 characters.

Does this port of CVS support response files?  If it does, you could
try invoking CVS via Bash, since Bash automatically uses a response
file with non-DJGPP programs when the command line is too long.

I have an experimental version of `system' and related `spawn*'
functions which can pass long command lines to Windows programs via
the CMDLINE environment variable.  If you are desperate and aren't
afraid of using alpha-quality software, I can send you the sources of
the patched functions, but you will need to rebuild Perl after
patching your libc.