| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
Notes:
svn path=/head/; revision=412346
|
|
|
|
| |
Notes:
svn path=/head/; revision=397182
|
|
|
|
| |
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=348159
|
|
DBIx::Admin::CreateTable is a pure Perl module.
Database vendors supported: MySQL, Oracle, Postgres, SQLite.
Assumptions:
- Every table has a primary key
- The primary key is a unique, non-null, integer
- The primary key is a single column
- The primary key column is called 'id'
- If a primary key has a corresponding auto-created index, the index is called
't_pkey': This is true for Postgres, where declaring a column as a primary
key automatically results in the creation of an associated index for that
column. The index is named after the table, not after the column.
- If a table 't' (with primary key 'id') has an associated sequence, the
sequence is called 't_id_seq': This is true for both Oracle and Postgres,
which use sequences to populate primary key columns. The sequences are named
after both the table and the column.
WWW: http://search.cpan.org/dist/DBIx-Admin-CreateTable/
Notes:
svn path=/head/; revision=347896
|