summaryrefslogtreecommitdiff
path: root/databases/p5-DBM-Deep
diff options
context:
space:
mode:
authorsno <sno>2010-08-21 06:07:39 +0000
committersno <sno>2010-08-21 06:07:39 +0000
commitfb671b178bf1778bb4e1c93379981a2e69b5e0fe (patch)
treeb5994e8dbbe6069ef61162c7d524f3ba12fc474d /databases/p5-DBM-Deep
parent038ff105504e6ee7590817c481cc36bce8afadef (diff)
downloadpkgsrc-fb671b178bf1778bb4e1c93379981a2e69b5e0fe.tar.gz
Updating databases/p5-DBM-Deep from 1.0025 to 2.0000
Upstream changes: 2.0000 Jul 18 14:30:00 2010 PDT - THIS VERSION IS NOT FULLY COMPATIBLE WITH 1.002x. - This version is practically identical to the previous dev release. See 1.9999_01, below, for all the hype. - Also, a memory leak caused by misuse of field hashes has been fixed. - perl 5.8.4 is now required. 1.9999_02 Jul 11 13:02:00 2010 PDT (This is the second developer release for 2.0000.) - Fixed a broken test - Fixed compilation and overloading under perl 5.8.x 1.9999_01 Jun 27 14:22:00 2010 PDT (This is the first developer release for 2.0000.) - THIS VERSION CHANGES THE FILE FORMAT. - Databases from DBM::Deep 1.0003 and higher can still be opened. - Newly-created databases automatically use the version 2.x format (numbered 4 internally), which version 1.x cannot open. - The optimize method, since it copies everything to a new database, upgrades it. - There is a new db_version method. - Support for perl 5.6 has been dropped. We now require 5.8. 5.6 users can still use version 1.0025. If anyone really needs 5.6 support in version 2.x, we can add it back again, but would pre- fer not to. Bug fixes may be back-ported to 1.002x if requested. - The File back end now supports Unicode. This is only supported for new databases. Old databases in the DBM::Deep 1.0003 format will have to be upgraded for this to work. - New external_refs mode, which allows objects retrieved from the database to hang on to the corresponding database entries, keep- ing them alive, even after all references to them from the data- base itself have been deleted. - Numeric comparison of DBM::Deep objects now works. Different objects used to compare equal. And there were uninitial- ized warnings. - Deletions now work properly in the DBI back end. Deleting an array or hash referenced by two keys in the database used to be a no-op.
Diffstat (limited to 'databases/p5-DBM-Deep')
-rw-r--r--databases/p5-DBM-Deep/Makefile4
-rw-r--r--databases/p5-DBM-Deep/distinfo8
2 files changed, 6 insertions, 6 deletions
diff --git a/databases/p5-DBM-Deep/Makefile b/databases/p5-DBM-Deep/Makefile
index 70c82ff5090..9005071c714 100644
--- a/databases/p5-DBM-Deep/Makefile
+++ b/databases/p5-DBM-Deep/Makefile
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.7 2010/06/12 16:00:44 seb Exp $
+# $NetBSD: Makefile,v 1.8 2010/08/21 06:07:39 sno Exp $
-DISTNAME= DBM-Deep-1.0025
+DISTNAME= DBM-Deep-2.0000
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 7fed6d0fabd..80d27ab89c4 100644
--- a/databases/p5-DBM-Deep/distinfo
+++ b/databases/p5-DBM-Deep/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.6 2010/06/12 16:00:44 seb Exp $
+$NetBSD: distinfo,v 1.7 2010/08/21 06:07:39 sno Exp $
-SHA1 (DBM-Deep-1.0025.tar.gz) = cbc57b7823d4237c5703cf234e162b9200eb2693
-RMD160 (DBM-Deep-1.0025.tar.gz) = bf0626555ad395e7989394345d913eb09801263a
-Size (DBM-Deep-1.0025.tar.gz) = 168379 bytes
+SHA1 (DBM-Deep-2.0000.tar.gz) = 2887817228bf8369ef00638cffed28f4d2094858
+RMD160 (DBM-Deep-2.0000.tar.gz) = a568978191f50f534cc0bcbecf0f9bec98981986
+Size (DBM-Deep-2.0000.tar.gz) = 175669 bytes
SHA1 (patch-aa) = aeb979ec48d0b984bf8b82770d1aa48bf3d00fb3