DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:mime-version:content-type
	:content-transfer-encoding:message-id:date:to:subject; q=dns; s=
	default; b=Bi2weNy5LoPwP9dhvEEDo8tKkrWpKnKeVp97cMwS0P5mkhdOaDNS7
	nLPu91IreBjCafjBksfGRHhD8cckisYae/5F4do6oMelupKZOKLHshH0i4RlnjrU
	/eBtqSA0sk9uFzPJD4dV+OzL2fFOj/yvfTqS5clWqjSfwyOD+UnrUk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Dr Rainer Woitok <rainer DOT woitok AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <22062.2952.946000.358554@woitok.gmail.com>
Date: Mon, 26 Oct 2015 12:16:24 +0100
To: cygwin AT cygwin DOT com
Subject: Command line length in Ash or Dash Shells

Fellow Cygwinners,

recently I needed to remove quite a few Cygwin packages from my install-
ation, and due to  all these interdependencies  I wanted to do this in a
single call:

   setup-x86*.exe -x ...,...,...

Calling this  command as  a Windows  "*.bat" file  failed with  an error
message suggesting that the command line simply was too long.  Searching
the web I  found disagreeing figures for the maximum command line length
for "*bat" files  under Windows Vista of  2000+ and 8000+,  but since my
command line had a length of  12000+ anyway,  I tried issuing this comm-
and from an Ash Shell script instead, which succeeded.

No I'm  playing with the idea  of using such an  Ash Shell script  (with
"setup-x86*.exe -P", of course)  to carry my current Cygwin implementat-
ion over to my  not yet decided upon next hardware.   But nevertheless I
feel a bit uneasy  about any potential  command line length  restriction
which could ultimately raise  its ugly head and interfere with my glori-
ous plans.

Does anybody definitely know about a  maximum command line length in the
Ash or Dash Shells?

Or alternatively:  is there a way to cause  "setup-x86*.exe" to read the
package list from a file or from standard input, even though "setup-x86*
--help" does not seem to indicate there is?

Any pointers appreciated.

Sincerely,
  Rainer

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple