[pkgsrc/trunk]: pkgsrc/databases/p5-DBD-Mock Import p5-DBD-Mock version 1.39.

[he <he%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/e87f10c41899
branches:  trunk
changeset: 552884:e87f10c41899
user:      he <he%pkgsrc.org@localhost>
date:      Sun Jan 11 13:50:20 2009 +0000

description:
Import p5-DBD-Mock version 1.39.

Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions
about your environment and ask the user to provide relevant connection
information. But if you need to test a framework that uses DBI,
particularly a framework that uses different types of persistence
schemes, then it may be more useful to simply verify what the
framework is trying to do -- ensure the right SQL is generated and
that the correct parameters are bound. DBD::Mock makes it easy to
just modify your configuration (presumably held outside your code)
and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql)
in your framework.

diffstat:

 databases/p5-DBD-Mock/DESCR    |  11 +++++++++++
 databases/p5-DBD-Mock/Makefile |  22 ++++++++++++++++++++++
 databases/p5-DBD-Mock/distinfo |   5 +++++
 3 files changed, 38 insertions(+), 0 deletions(-)

diffs (50 lines):

diff -r 23540bd307d4 -r e87f10c41899 databases/p5-DBD-Mock/DESCR
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/databases/p5-DBD-Mock/DESCR       Sun Jan 11 13:50:20 2009 +0000
@@ -0,0 +1,11 @@
+Testing with databases can be tricky. If you are developing a system
+married to a single database then you can make some assumptions
+about your environment and ask the user to provide relevant connection
+information. But if you need to test a framework that uses DBI,
+particularly a framework that uses different types of persistence
+schemes, then it may be more useful to simply verify what the
+framework is trying to do -- ensure the right SQL is generated and
+that the correct parameters are bound. DBD::Mock makes it easy to
+just modify your configuration (presumably held outside your code)
+and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql)
+in your framework.
diff -r 23540bd307d4 -r e87f10c41899 databases/p5-DBD-Mock/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/databases/p5-DBD-Mock/Makefile    Sun Jan 11 13:50:20 2009 +0000
@@ -0,0 +1,22 @@
+# $NetBSD: Makefile,v 1.1.1.1 2009/01/11 13:50:20 he Exp $
+#
+
+DISTNAME=      DBD-Mock-1.39
+PKGNAME=       p5-${DISTNAME}
+SVR4_PKGNAME=  p5ddm
+CATEGORIES=    databases perl5
+MASTER_SITES=  ${MASTER_SITE_PERL_CPAN:=DBD/}
+
+MAINTAINER=    pkgsrc-users%NetBSD.org@localhost
+HOMEPAGE=      http://search.cpan.org/dist/DBD-Mock/
+COMMENT=       Perl5 module with mock database driver for testing
+
+PKG_DESTDIR_SUPPORT=   user-destdir
+
+DEPENDS+=      p5-DBI>=1.3:../../databases/p5-DBI
+
+PERL5_PACKLIST=        auto/DBD/Mock/.packlist
+PERL5_MODULE_TYPE=     Module::Build
+
+.include "../../lang/perl5/module.mk"
+.include "../../mk/bsd.pkg.mk"
diff -r 23540bd307d4 -r e87f10c41899 databases/p5-DBD-Mock/distinfo
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/databases/p5-DBD-Mock/distinfo    Sun Jan 11 13:50:20 2009 +0000
@@ -0,0 +1,5 @@
+$NetBSD: distinfo,v 1.1.1.1 2009/01/11 13:50:20 he Exp $
+
+SHA1 (DBD-Mock-1.39.tar.gz) = e65ccba456569366efffc292e501763988962b3f
+RMD160 (DBD-Mock-1.39.tar.gz) = 93de4bd2f3430a013e7f422ae1ed686b30db8d82
+Size (DBD-Mock-1.39.tar.gz) = 39785 bytes