summaryrefslogtreecommitdiff
path: root/databases/p5-DBD-Mock
diff options
context:
space:
mode:
authorhe <he>2009-01-11 13:50:20 +0000
committerhe <he>2009-01-11 13:50:20 +0000
commitbb092950639fe50ff23181201cb23bce0260533a (patch)
tree939c1798a41a95c31242944237aeb02044a62245 /databases/p5-DBD-Mock
parentda71bfbb95e7b3baa5f03f5c6687e57fef041be2 (diff)
downloadpkgsrc-bb092950639fe50ff23181201cb23bce0260533a.tar.gz
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 (limited to 'databases/p5-DBD-Mock')
-rw-r--r--databases/p5-DBD-Mock/DESCR11
-rw-r--r--databases/p5-DBD-Mock/Makefile22
-rw-r--r--databases/p5-DBD-Mock/distinfo5
3 files changed, 38 insertions, 0 deletions
diff --git a/databases/p5-DBD-Mock/DESCR b/databases/p5-DBD-Mock/DESCR
new file mode 100644
index 00000000000..0dc40d7dece
--- /dev/null
+++ b/databases/p5-DBD-Mock/DESCR
@@ -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 --git a/databases/p5-DBD-Mock/Makefile b/databases/p5-DBD-Mock/Makefile
new file mode 100644
index 00000000000..6b11e969210
--- /dev/null
+++ b/databases/p5-DBD-Mock/Makefile
@@ -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
+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 --git a/databases/p5-DBD-Mock/distinfo b/databases/p5-DBD-Mock/distinfo
new file mode 100644
index 00000000000..9fb9d679c7c
--- /dev/null
+++ b/databases/p5-DBD-Mock/distinfo
@@ -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