| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
Notes:
svn path=/head/; revision=412346
|
| |
|
|
| |
Notes:
svn path=/head/; revision=397180
|
| |
|
|
| |
Notes:
svn path=/head/; revision=374290
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=373448
|
| |
|
|
| |
Notes:
svn path=/head/; revision=371255
|
| |
|
|
| |
Notes:
svn path=/head/; revision=348160
|
|
|
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/
Notes:
svn path=/head/; revision=347898
|
