Front page | perl.perl1.porters |
Postings from February 2008
I believe that this fix also needs applying to Perl 1, as I found the same
error in 1.0's Configure script.
I doubt anyone can find a Perl bug older than this one :-)
Nicholas Clark
----- Forwarded message from Nicholas Clark <nwc10+p5p4@colon.colondot.net> -----
Envelope-to: nick@ccl4.org
Delivery-date: Fri, 15 Feb 2008 14:30:32 +0000
Delivered-To: perl5-changes@perl.org
From: Nicholas Clark <nwc10+p5p4@colon.colondot.net>
To: "Anybody And Everybody" <perl5-changes@perl.org>
Subject: Change 33318: Shell patterns are subject to tilde expansion. So the case statement
Date: Fri, 15 Feb 2008 06:30:03 -0800 (PST)
Change 33318 by nicholas@minne on 2008/02/15 14:27:55
Shell patterns are subject to tilde expansion. So the case statement
in the filexp script (written out by Configure) for expanding ~ and
~/* has never worked. It's always been relying on the /bin/csh glob
for the ~* case. Few people ever noticed because one has to be
building to one's home directory on a system with no csh installed.
This is a bug from Perl 1.0's Configure!
Affected files ...
... //depot/perl/Configure#683 edit
Differences ...
==== //depot/perl/Configure#683 (xtext) ====
Index: perl/Configure
--- perl/Configure#682~33049~ 2008-01-23 01:18:41.000000000 -0800
+++ perl/Configure 2008-02-15 06:27:55.000000000 -0800
@@ -3589,7 +3589,7 @@
$startsh
: expand filename
case "\$1" in
- ~/*|~)
+ \~/*|\~)
echo \$1 | $sed "s|~|\${HOME-\$LOGDIR}|"
;;
~*)
End of Patch.
----- End forwarded message -----
Thread Next