13:08 mat 

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

 

11:44 sunpoet 

- Update to 500.002
- Use single space after WWW:
- While I'm here:
  - Add LICENSE
  - Remove unnecessary MASTER_SITE_SUBDIR
  - Sort *_DEPENDS
  - Use TEST_DEPENDS

Changes:	http://search.cpan.org/dist/NetApp/CHANGES
PR:		ports/185417
Submitted by:	Hung-Yi Chen <gaod@hychen.org>
Approved by:	snowfly <snowfly@yuntech.edu.tw> (maintainer)

 

13:12 ehaupt 

Support staging.

 

02:03 pgollucci 

- only 13% of the p5- ports embed @comment $FreeBSD$:
  so standarize and remove it

With Hat:   perl@

15:13 rafan 

This package provides a suite of modules for managing NetApp's NAS
devices, commonly referred to as "filers".

This is the first public release of my NetApp Perl API, and although I
consider the code to be very stable, the API should be considered
experimental.  The convention I will be following regarding
non-compatible API changes is as follows.  I'm using a
major.minor.subminor release naming convention, and I will promise to
NOT make non-backwards compatible changes between subminor releases.

However, in order to allow the API to evolve, it is entirely possible
that non-backwards compatible changes will be made between minor
releases.  IOW, the major.minor release numbers can be considered an
API version.  Any changes to 1.1.0, 1.1.2, etc. must be backwards
compatible with the previous 1.1.* releases.

There is no guarantee that 1.2.0 will be 100% backwards compatible,
although such changes will be made only when justified.  The author
does not believe in infinite backwards compatibility.

WWW:    http://search.cpan.org/dist/NetApp/

PR:             ports/131166
Submitted by:   Tsung-Han Yeh <snowfly at yuntech.edu.tw>