Update p5-DBM-Deep from version 1.0016 to version 1.0020.

Upstream changes:
1.0023 May 9 14:33:00 2010 PDT
    (This version is compatible with 1.0022)
    - The DBI back end no longer dies with ?<80><98>Use of uninitialized value
      $_ in lc?<80><99> in perl 5.12.0. Thanks to Ansgar Burchardt for finding
      and fixing this problem.

1.0022 Apr 25 18:40:00 2010 PDT
    (This version is compatible with 1.0021)
    - Singleton support has been re-enabled in the File back end.
    - t/43_transaction_maximum.t was still failing on some systems
      (see http://www.cpantesters.org/cpan/report/7151810), so now we
      try to detect the maximum number of files we can open.

1.0021 Apr 18 18:28:00 2010 PDT
    (This version is compatible with 1.0020)
    - Correct spelling mistakes in the documentation (thanks to Gregor
      Herrmann for the corrections and to Ansgar Burchardt for passing
      them on) (RT#56520)
    - MANIFEST now lists the test libs so they get included in the
      distribution (RT#56512)
    - It no longer crashes in perl 5.6.2.

1.0020 Feb 16 22:00:00 2010 EST
    (This version is compatible with 1.0016)
	- Fixed t/43_transaction_maximum.t so that it doesn't error out on systems
      which cannot fork > 255 children at one time.
    - Improved code coverage
        - Added t/96_virtual_functions.t which helps describe what actually
          needs to be overridden in a new plugin.


1.0019_003 Feb 16 22:00:00 2010 EST
    (This is the third developer release for 1.0020.)
    (This version is compatible with 1.0016)
	- Fixed problem where "./Build test" wouldn't actually -do- anything.
        - (No-one apparently tried to install this till Steven Lembark. Thanks!)
    - Fixed speed regression with keys in the File backend.
        - Introduced in 1.0019_002 to fix #50541
        - Thanks, SPROUT!
    - (RT #53575) Recursion failure in STORE (Thanks, SPROUT)
    - Merged the rest of the fixes from 1.0015 and 1.0016
        - Thanks to our new co-maintainer, SPROUT! :)
    - Had to turn off singleton support in the File backend because the caching
      was causing havoc with transactions. Turning on fatal warnings does give
      apparently important information.
    - Oh - forgot to mention that fatal warnings are now on in all files.

1.0019_002 Jan 05 22:30:00 2010 EST
    (This is the second developer release for 1.0020.)
    (This version is compatible with 1.0014)
	- Fixed bug where attempting to store a value tied to something other than
      DBM::Deep would leave the file flocked.
	- Added support for DBD::SQLite
        - Build.PL has been extended to support sqlite vs. mysql
        - Storage::DBI now detects between the two DBDs
    - (RT #51888) Applied POD patch (Thanks, FWIE!)
    - (RT #44981) Added VERSION to ::Array, ::Engine, and ::Hash
    - Removed extraneous slashes from POD links (Thanks ilmari!)
    - (RT #50541) Fixed bug in clear() for hashes in the File backend.
        - This has caused a regression in speed for clear() when clearing
          large hashes using running with the File backend. ->clear() (on my
          machine) now takes ( N / 40 ) ** (1.66) seconds. So, clearing 4000
          keys (as is the test in t/03_bighash.t) would take ~2070 seconds.
    - (RT #40782) Fixed bug when handling a key of '0' (Thanks Sterling!)
    - (RT #48031) Fixed bug with localized $, (Thanks, SPROUT!)

1.0019_001 Dec 31 22:00:00 2009 EST
    (This is the first developer release for 1.0020.)
    (This version is compatible with 1.0014)
	- DBM::Deep has been refactored to allow for multiple engines. There are two
      engines built so far:
        - File (the original engine)
        - DBI (an engine based on DBI)
    - The DBI engine has only been tested on MySQL and isn't transactional.
        - InnoDB sucks horribly. When run in a sufficient isolation mode, it
          creates deadlocks.
    - A custom Build.PL has been written to allow for running tests under
      CPAN.pm against the various engines.
        - This also allows running the long tests under CPAN.pm
    - This has meant a ton of refactoring. Hopefullly, this refactoring will
      allow finding some of the niggly bugs more easily. Those tests have not
      been enabled yet. That's the next developer release.
    - Hopefully, this multi-engine support will allow deprecation of the file
      format in the future.

3 files changed, 26 insertions, 6 deletions

diff --git a/databases/p5-DBM-Deep/Makefile b/databases/p5-DBM-Deep/Makefile
index 7ce8c4af55f..1983adb7054 100644
--- a/databases/p5-DBM-Deep/Makefile
+++ b/databases/p5-DBM-Deep/Makefile
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.5 2010/03/10 08:46:57 sno Exp $
+# $NetBSD: Makefile,v 1.6 2010/05/24 13:22:51 seb Exp $
 
-DISTNAME=	DBM-Deep-1.0016
+DISTNAME=	DBM-Deep-1.0023
 PKGNAME=	p5-${DISTNAME}
 CATEGORIES=	databases perl5
 MASTER_SITES=	${MASTER_SITE_PERL_CPAN:=DBM/}
diff --git a/databases/p5-DBM-Deep/distinfo b/databases/p5-DBM-Deep/distinfo
index 71134b133c0..96f75acf312 100644
--- a/databases/p5-DBM-Deep/distinfo
+++ b/databases/p5-DBM-Deep/distinfo
@@ -1,5 +1,6 @@
-$NetBSD: distinfo,v 1.4 2010/03/10 08:46:57 sno Exp $
+$NetBSD: distinfo,v 1.5 2010/05/24 13:22:51 seb Exp $
 
-SHA1 (DBM-Deep-1.0016.tar.gz) = 2ae043df9c8a8c31a8bbe9dd2684eb0a2d725435
-RMD160 (DBM-Deep-1.0016.tar.gz) = 355aa64759a0815381ccce3e69eb582dfed15a6e
-Size (DBM-Deep-1.0016.tar.gz) = 152690 bytes
+SHA1 (DBM-Deep-1.0023.tar.gz) = 4ad6ba4587d9db80ca5edee7d1d388cf7e2c9629
+RMD160 (DBM-Deep-1.0023.tar.gz) = 3a23c4aebb0ff0ab7bb83df31935cc2c95bf3ba5
+Size (DBM-Deep-1.0023.tar.gz) = 166665 bytes
+SHA1 (patch-aa) = 00674ebce2703a5ff36dde418e16f8e89edf3057
diff --git a/databases/p5-DBM-Deep/patches/patch-aa b/databases/p5-DBM-Deep/patches/patch-aa
new file mode 100644
index 00000000000..eb918839f77
--- /dev/null
+++ b/databases/p5-DBM-Deep/patches/patch-aa
@@ -0,0 +1,19 @@
+$NetBSD: patch-aa,v 1.1 2010/05/24 13:22:51 seb Exp $
+
+Configure must not be interactive.
+
+--- Build.PL.orig	2010-04-10 14:49:51.000000000 +0000
++++ Build.PL
+@@ -70,9 +70,9 @@ my $build = Module::Build->subclass(
+     },
+ );
+ 
+-if ( $build->y_n( "Run the long-running tests", 'n' ) ) {
+-    $build->notes( 'LONG_TESTS' => 1 );
+-}
++#if ( $build->y_n( "Run the long-running tests", 'n' ) ) {
++#    $build->notes( 'LONG_TESTS' => 1 );
++#}
+ 
+ if ( $build->features( 'sqlite_engine' ) ) {
+     if ( $build->y_n( "Run the tests against the DBI engine via SQLite?", 'n' ) ) {