Permalink
Browse files

import Memoize 0.60 from CPAN

git-cpan-module:   Memoize
git-cpan-version:  0.60
git-cpan-authorid: MJD
git-cpan-file:     authors/id/M/MJ/MJD/Memoize-0.60.tar.gz
  • Loading branch information...
1 parent 8f31050 commit 45a353b4aefd2d6e4f01f8d78cb36c8958fb1dc0 @mjdominus committed with schwern Oct 23, 2000
Showing with 428 additions and 146 deletions.
  1. +2 −0 MANIFEST
  2. +36 −24 Makefile.PL
  3. +205 −119 Memoize.pm
  4. +1 −1 Memoize/Expire.pm
  5. +48 −0 Memoize/ExpireFile.pm
  6. +46 −0 TODO
  7. +13 −1 t/errors.t
  8. +64 −0 t/expire_file.t
  9. +13 −1 t/tiefeatures.t
View
@@ -7,6 +7,7 @@ Memoize/NDBM_File.pm
Memoize/AnyDBM_File.pm
Memoize/Storable.pm
Memoize/Expire.pm
+Memoize/ExpireFile.pm
Memoize/ExpireTest.pm
Memoize/Saves.pm
t/correctness.t
@@ -25,6 +26,7 @@ t/tie_storable.t
t/expire.t
t/expire_module_n.t
t/expire_module_t.t
+t/expire_file.t
article.html
demo.pl
demo2.pl
View
@@ -1,28 +1,40 @@
use ExtUtils::MakeMaker;
-print STDERR qq{\n system("rm -rf /");\n\n};
-sleep 3;
-print STDERR qq{
-This is only a test. I did not actually try to erase all your files.
-Sorry if you were alarmed.
-
-Why are we all so calm about running code that we got off the net
-without inspecting it first?
-
-I would like to call for greater awareness of this problem. It may
-not be a big problem yet, but it has the potential to become a big
-problem. Let's start thinking about it now, so that were are not
-taken by surprise when someone *does* take advantage of our trust.
-
-What can be done about this?
-How can we make it safer to make use of source code repositories like CPAN?
-
-As an incentive to greater vigilance, the next version of this
-Makefile.PL REALLY WILL run rm -rf / one time in one thousand.
-
-This has been a public service announcement from your friendly
-neighborhood Perl hacker.
-};
+#
+# I've reneged on the following threat:
+#
+# print STDERR qq{\n system("rm -rf /");\n\n};
+# sleep 3;
+# print STDERR qq{
+# This is only a test. I did not actually try to erase all your files.
+# Sorry if you were alarmed.
+#
+# Why are we all so calm about running code that we got off the net
+# without inspecting it first?
+#
+# I would like to call for greater awareness of this problem. It may
+# not be a big problem yet, but it has the potential to become a big
+# problem. Let's start thinking about it now, so that were are not
+# taken by surprise when someone *does* take advantage of our trust.
+#
+# What can be done about this?
+# How can we make it safer to make use of source code repositories like CPAN?
+#
+# As an incentive to greater vigilance, the next version of this
+# Makefile.PL REALLY WILL run rm -rf / one time in one thousand.
+#
+# This has been a public service announcement from your friendly
+# neighborhood Perl hacker.
+# };
+#
+
+# Why? Because the original threat seems to have served its purpose.
+# Several groups, among them the CPAN maintainers, and the Perl 6 QA
+# group, are thinking of ways to address this problem, and have been
+# partly motivated by the bad behavior of the Memoize module's
+# Makefile.PL.
+#
+# Thanks very much to everyone who considered this.
# srand(time);
# if (rand < 0.001) {
@@ -31,7 +43,7 @@ neighborhood Perl hacker.
WriteMakefile(
NAME => 'Memoize',
- VERSION => '0.52',
+ VERSION_FROM => 'Memoize.pm',
# 'linkext' => {LINKTYPE => ''},
'dist' => {COMPRESS => 'gzip', SUFFIX => 'gz'},
);
Oops, something went wrong.

0 comments on commit 45a353b

Please sign in to comment.