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
think mrtg with xml configs
Torrus is designed to be the universal data series processing framework.
Although most users deploy Torrus for SNMP monitoring, it might be useful for
data series of any nature. Tobi Oetiker's RRDtool is used for data storage.
* Configuration compiler and validator. It processes the XML configuration
files and saves the configuration into a database.
* View renderer and the web interface. They generate HTML and the graphical
representation of the datasources and provide user authentication and
authorization. All generated output is controlled by the configuration
parameters and templates. The users can easily create their own
presentation of data series.
* SNMP Collector. Modular collector core architecture allows further
extension with new collector and storage types. Any datasource can have
its own polling schedule.
* SNMP Device Discovery Tool. Devdiscover is a new, modular, flexible, and
expandable tool for automatic generation of Torrus configuration files.
New device types and MIBs are easily added as independent Perl modules.
* Threshold monitor. All data, regardless of their type and nature, can be
monitored according to the user-defined rules. The rules can also include
the datasource-specific parameters, e.g. boundary values etc. The
thresholds are specified by RPN expressions.
WWW: http://torrus.org
- Corey Smith
corsmith@gmail.com
PR: ports/86634
Submitted by: Corey Smith <corsmith@gmail.com>
