The vSphere SDK for Perl provides an easy-to-use Perl scripting interface to
the vSphere API. SDK ships with utilities, and documentation for building
vSphere management applications.
The vSphere Command-Line Interface (vSphere CLI) command set allows you to
run common system administration commands against ESX/ESXi systems from any
machine with network access to those systems. You can also run most vSphere
CLI commands against a vCenter Server system and target any ESX/ESXi system
that vCenter Server system manages.
vSphere CLI commands are especially useful for ESXi hosts because ESXi does
not include a service console.
Please note that, by default, an underlying Perl module does certificate
verification when communicating with vSphere hosts.
You must create a file that contains the public keys of all of your
vSphere hosts and then configure your Perl scripts to have the following
line:
$ENV{HTTPS_CA_FILE} = "/path/to/file";
If you want to disable this important security feature, you may set the
following variable to 0:
$ENV{PERL_LWP_SSL_VERIFY_HOSTNAME}
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* <ports@c0decafe.net>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Straup Cope <ascope@cpan.org>
* Aaron Zauner <az_mail@gmx.at>
* Adam Jette <jettea46@yahoo.com>
* Adam Weinberger <adamw@FreeBSD.org>
* Alan Eldridge <alane@geeksrus.net>
* Alex Bakhtin <Alex.Bakhtin@gmail.com>
* Alex Deiter <Alex.Deiter@Gmail.COM>
* Alex Dupre <ale@FreeBSD.org>
* Alex Dupre <sysadmin@alexdupre.com>
(Only the first 15 lines of the commit message are shown above )
Update to 6.7.0
You can use the vSphere SDK for Perl to manage
* ESXi 5.x
* ESXi 6.x
* vCenter Server 5.x
* vCenter Server 6.x
Approved by: zi (maintainer via private msg)
Remove libexpat.so.6 compatibility link that was added in r374303 to
prevent massive PORTREVISION bumps. Bump dependent ports that have not
been bumped since.
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
(Only the first 15 lines of the commit message are shown above )
Multiple ports: reset maintainers
Maintainers for these ports have been notified on 5 separate occasions
over the course of several months about pending actions required.
We really appreciate the time and effort you put in to maintain
these ports.
If you are still interested in helping to maintain these ports just
reply to me or file a PR and I will happily assign the port to you
again.
Approved by: portmgr (implicit)
The vSphere SDK for Perl provides an easy-to-use Perl scripting interface to
the vSphere API. SDK ships with utilities, and documentation for building
vSphere management applications.
The vSphere Command-Line Interface (vSphere CLI) command set allows you to
run common system administration commands against ESX/ESXi systems from any
machine with network access to those systems. You can also run most vSphere
CLI commands against a vCenter Server system and target any ESX/ESXi system
that vCenter Server system manages.
vSphere CLI commands are especially useful for ESXi hosts because ESXi does
not include a service console.
WWW: http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_4/
PR: ports/158753
Submitted by: rpsfa at rit.edu
