Update of patch#41 (group libtool):
Status:None => Wont Do
Open/Closed:Open => Closed
___
Follow-up Comment #2:
The patch no longer
On Fri, Oct 26, 2001 at 09:12:19AM +0100, Olly Betts wrote:
On Thu, Oct 25, 2001 at 02:43:23PM -0500, Robert Boehne wrote:
+ if test `expr X$rmfiles : .*` -gt $max_cmd_len; then
How portable is test -gt? The Goat book doesn't list it as a portable
test operator:
Jeff Dubrule wrote:
On Wed, Oct 24, 2001 at 09:21:48AM -0500, Robert Boehne wrote:
Libtool saves a good guess for the maximum length
of command lines as max_cmd_len so if you wanted to
support removing files up to an average of 99 characters
you could divide max_cmd_len by 100 to get
Jeff:
Heh, yeah, this is getting more complex isn't it. :)
Libtool saves a good guess for the maximum length
of command lines as max_cmd_len so if you wanted to
support removing files up to an average of 99 characters
you could divide max_cmd_len by 100 to get the number
of files to delete at a
On Wed, Oct 24, 2001 at 09:21:48AM -0500, Robert Boehne wrote:
Libtool saves a good guess for the maximum length
of command lines as max_cmd_len so if you wanted to
support removing files up to an average of 99 characters
you could divide max_cmd_len by 100 to get the number
of files to
Hmm. I was having trouble trying to feed 'xargs' it's data without
actually putting it all on a command-line at some point(silly, eh?).
In any event, perhaps something like this will work:
for each file
...
$rmfiles=$rmfiles $some_files_to_delete
...
if 100 -l
