Have Makefile.PL touch the CHANGES file so that "make dist" will find

it. Even though we generate CHANGES from the CVS log, WriteMakeFile needs to see something there first.
rcaputo · Jun 8, 2002 · 0ffdc69 · 0ffdc69
1 parent 11db5d3
commit 0ffdc69
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/mylib/Makefile-5004.pm b/mylib/Makefile-5004.pm
@@ -10,8 +10,8 @@ sub MY::test {
   "\ntest ::\n\t\$(FULLPERL) ./lib/deptest.perl\n" . shift->SUPER::test(@_);
 }
 
-# See lib/ExtUtils/MakeMaker.pm for details of how to influence the
-# contents of the Makefile that is written.
+# Touch CHANGES so it exists.
+open(CHANGES, ">>CHANGES") and close CHANGES;
 
 WriteMakefile
   ( NAME           => 'POE',

diff --git a/mylib/Makefile-5005.pm b/mylib/Makefile-5005.pm
@@ -76,7 +76,7 @@ ExtUtils::AutoInstall->import
 );
 
 # Touch CHANGES so it exists.
-# open(CHANGES, ">>CHANGES") and close CHANGES;
+open(CHANGES, ">>CHANGES") and close CHANGES;
 
 WriteMakefile
   ( NAME           => 'POE',