kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/databases/p5-DBIx-Admin-DSNManager/Makefile

29 lines
699 B
Makefile
Raw Normal View History

- 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/
2014-03-11 19:01:06 +01:00
# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
# $FreeBSD$
PORTNAME= DBIx-Admin-DSNManager
PORTVERSION= 2.01
Change the way Perl modules are installed, update the default Perl to 5.18. Before, we had: site_perl : lib/perl5/site_perl/5.18 site_perl/perl_arch : lib/perl5/site_perl/5.18/mach perl_man3 : lib/perl5/5.18/man/man3 Now we have: site_perl : lib/perl5/site_perl site_arch : lib/perl5/site_perl/mach/5.18 perl_man3 : lib/perl5/site_perl/man/man3 Modules without any .so will be installed at the same place regardless of the Perl version, minimizing the upgrade when the major Perl version is changed. It uses a version dependent directory for modules with compiled bits. As PERL_ARCH is no longer needed in plists, it has been removed from PLIST_SUB. The USE_PERL5=fixpacklist keyword is removed, the .packlist file is now always removed, as is perllocal.pod. The old site_perl and site_perl/arch directories have been kept in the default Perl @INC for all Perl ports, and will be phased out as these old Perl versions expire. PR: 194969 Differential Revision: https://reviews.freebsd.org/D1019 Exp-run by: antoine Reviewed by: perl@ Approved by: portmgr
2014-11-26 14:08:24 +01:00
PORTREVISION= 1
- 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/
2014-03-11 19:01:06 +01:00
CATEGORIES= databases perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Manage a file of DSNs, for both testing and production
LICENSE= ART20
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g. With hat: portmgr Sponsored by: Absolight
2016-04-01 16:00:51 +02:00
BUILD_DEPENDS= p5-Config-Tiny>=2.12:devel/p5-Config-Tiny \
p5-DBI>=0:databases/p5-DBI \
p5-File-Slurp>=9999.13:devel/p5-File-Slurp \
p5-Moo>=1.004002:devel/p5-Moo
- 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/
2014-03-11 19:01:06 +01:00
RUN_DEPENDS:= ${BUILD_DEPENDS}
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g. With hat: portmgr Sponsored by: Absolight
2016-04-01 16:00:51 +02:00
TEST_DEPENDS= p5-Test-Version>=1.002003:devel/p5-Test-Version \
p5-Try-Tiny>=0.06:lang/p5-Try-Tiny
- 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/
2014-03-11 19:01:06 +01:00
- Add NO_ARCH
2015-09-17 19:13:28 +02:00
NO_ARCH= yes
- 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/
2014-03-11 19:01:06 +01:00
USE_PERL5= configure
- Use USES=tar:tgz
2014-03-14 08:44:49 +01:00
USES= perl5 tar:tgz
- 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/
2014-03-11 19:01:06 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink