- Add p5-DBIx-Admin-DSNManager 2.01

DBIx::Admin::DSNManager manages a file of DSNs, for both testing and production.

The INI-style format was selected, rather than, say, using an SQLite database,
so that casual users could edit the file without needing to know SQL and without
having to install the command line program sqlite3.

Each DSN is normally for something requiring manual preparation, such as
creating the database named in the DSN.

In the case of SQLite, etc, where manual intervention is not required, you can
still put the DSN in dsn.ini.

One major use of this module is to avoid environment variable overload, since it
is common to test Perl modules by setting the env vars $DBI_DSN, $DBI_USER and
$DBI_PASS.

But then the problem becomes: What do you do when you want to run tests against
a set of databases servers? Some modules define sets of env vars, one set per
database server, with awkward and hard-to-guess names. This is messy and
obscure.

DBIx::Admin::DSNManager is a solution to this problem.

WWW: http://search.cpan.org/dist/DBIx-Admin-DSNManager/

databases/Makefile

@@ -336,6 +336,7 @@
     SUBDIR += p5-DBIWrapper
     SUBDIR += p5-DBIx-Abstract
     SUBDIR += p5-DBIx-Admin-CreateTable
+    SUBDIR += p5-DBIx-Admin-DSNManager
     SUBDIR += p5-DBIx-AnyDBD
     SUBDIR += p5-DBIx-Browse
     SUBDIR += p5-DBIx-Class

databases/p5-DBIx-Admin-DSNManager/Makefile

@@ -0,0 +1,27 @@
+# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
+# $FreeBSD$
+
+PORTNAME=	DBIx-Admin-DSNManager
+PORTVERSION=	2.01
+CATEGORIES=	databases perl5
+MASTER_SITES=	CPAN
+PKGNAMEPREFIX=	p5-
+EXTRACT_SUFX=	.tgz
+
+MAINTAINER=	sunpoet@FreeBSD.org
+COMMENT=	Manage a file of DSNs, for both testing and production
+
+LICENSE=	ART20
+
+BUILD_DEPENDS=	p5-Config-Tiny>=2.12:${PORTSDIR}/devel/p5-Config-Tiny \
+		p5-DBI>=0:${PORTSDIR}/databases/p5-DBI \
+		p5-File-Slurp>=9999.13:${PORTSDIR}/devel/p5-File-Slurp \
+		p5-Moo>=1.004002:${PORTSDIR}/devel/p5-Moo
+RUN_DEPENDS:=	${BUILD_DEPENDS}
+TEST_DEPENDS=	p5-Test-Version>=1.002.003:${PORTSDIR}/devel/p5-Test-Version \
+		p5-Try-Tiny>=0.06:${PORTSDIR}/lang/p5-Try-Tiny
+
+USE_PERL5=	configure
+USES=		perl5
+
+.include <bsd.port.mk>

databases/p5-DBIx-Admin-DSNManager/distinfo

@@ -0,0 +1,2 @@
+SHA256 (DBIx-Admin-DSNManager-2.01.tgz) = e8c8a99ab82e6decbfec3523771f4a16de1005146f19164c47294e1f5d3aac6a
+SIZE (DBIx-Admin-DSNManager-2.01.tgz) = 10761

databases/p5-DBIx-Admin-DSNManager/pkg-descr

@@ -0,0 +1,24 @@
+DBIx::Admin::DSNManager manages a file of DSNs, for both testing and production.
+
+The INI-style format was selected, rather than, say, using an SQLite database,
+so that casual users could edit the file without needing to know SQL and without
+having to install the command line program sqlite3.
+
+Each DSN is normally for something requiring manual preparation, such as
+creating the database named in the DSN.
+
+In the case of SQLite, etc, where manual intervention is not required, you can
+still put the DSN in dsn.ini.
+
+One major use of this module is to avoid environment variable overload, since it
+is common to test Perl modules by setting the env vars $DBI_DSN, $DBI_USER and
+$DBI_PASS.
+
+But then the problem becomes: What do you do when you want to run tests against
+a set of databases servers? Some modules define sets of env vars, one set per
+database server, with awkward and hard-to-guess names. This is messy and
+obscure.
+
+DBIx::Admin::DSNManager is a solution to this problem.
+
+WWW: http://search.cpan.org/dist/DBIx-Admin-DSNManager/

databases/p5-DBIx-Admin-DSNManager/pkg-plist

@@ -0,0 +1,8 @@
+%%SITE_PERL%%/DBIx/Admin/DSNManager.pm
+%%SITE_PERL%%/%%PERL_ARCH%%/auto/DBIx/Admin/DSNManager/.packlist
+%%PERL5_MAN3%%/DBIx::Admin::DSNManager.3.gz
+@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/auto/DBIx/Admin/DSNManager
+@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/DBIx/Admin
+@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/DBIx
+@dirrmtry %%SITE_PERL%%/DBIx/Admin
+@dirrmtry %%SITE_PERL%%/DBIx