summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCraig A. Berry <craigberry@mac.com>2011-08-12 09:09:30 -0500
committerCraig A. Berry <craigberry@mac.com>2011-08-12 09:49:15 -0500
commitf4ef369354bb1dbebc128000108d3c4964e1cbf0 (patch)
tree37aef78011ecf47ab3c1acba2975fb0b4d95e87d
parent9825ce0e87f6a08192647f1352c92da16d377a04 (diff)
downloadperl-f4ef369354bb1dbebc128000108d3c4964e1cbf0.tar.gz
Clean up MANIFEST before creating a new one.
This is a follow-up to e4ac890e26c, which changed behavior from appending to an existing MANIFEST to creating a new one. On VMS, that would give us multiple versions, which probably wouldn't matter except that the tests insist that there is one and only one copy of every file they've created and they only clean up the highest version. The easiest way to handle this is to make sure we clean up first before creating a new MANIFEST file.
-rw-r--r--dist/ExtUtils-Manifest/lib/ExtUtils/Manifest.pm1
1 files changed, 1 insertions, 0 deletions
diff --git a/dist/ExtUtils-Manifest/lib/ExtUtils/Manifest.pm b/dist/ExtUtils-Manifest/lib/ExtUtils/Manifest.pm
index 62e9877982..40df070af7 100644
--- a/dist/ExtUtils-Manifest/lib/ExtUtils/Manifest.pm
+++ b/dist/ExtUtils-Manifest/lib/ExtUtils/Manifest.pm
@@ -730,6 +730,7 @@ sub _fix_manifest {
}
if ( $must_rewrite ) {
+ 1 while unlink $MANIFEST; # avoid multiple versions on VMS
open MANIFEST, ">", $MANIFEST or die "(must_rewrite=$must_rewrite) Could not open >$MANIFEST: $!";
for (my $i=0; $i<=$#manifest; $i+=2) {
print MANIFEST "$manifest[$i]\n";