You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@vcl.apache.org by "Curtis C." <se...@gmail.com> on 2012/06/26 01:00:28 UTC
RPM-ing VCL 2.2.1
Hi All,
I've been working on an initial spec file for VCL 2.2.1. Currently I
believe all the dependencies, CPAN modules included, can be obtained
from the EPEL and RPMForge repositories. If the project is going to
support RHEL and CentOS only then providing a RPM could allow you to
remove the requirement to run (and maintain) the perl libs install
script.
Still a bit more work to do, but I thought I would send it along
before I get too far to find out if anyone has
suggestions/comments/criticisms. :)
You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec
Right now it creates 3 packages: a main doc package (just contains the
sql files right now), a web package, and a management node package.
One question I have is about the:
use VMware::Vix::Simple;
use VMware::Vix::API::Constants
in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
with VCL and the official install docs don't ask to have them
installed either. But the rpmbuild process picks those modules up as
requirements.
Thanks,
Curtis.
Re: RPM-ing VCL 2.2.1
Posted by Everett Toews <ev...@cybera.ca>.
Great. I just created an issue for this at
https://issues.apache.org/jira/browse/VCL-602
Everett
On Mon, Jul 2, 2012 at 12:34 PM, Josh Thompson <jo...@ncsu.edu>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Everett,
>
> I'd definitely like to see rpms for installing VCL.
>
> Josh
>
> On Friday, June 29, 2012 9:24:03 AM Everett Toews wrote:
> > Does anyone on the VCL core dev team have an interest in this? Should we
> > create a JIRA issue for it?
> >
> > Regards,
> > Everett
> >
> > On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. <se...@gmail.com>
> wrote:
> > > Hi All,
> > >
> > > I've been working on an initial spec file for VCL 2.2.1. Currently I
> > > believe all the dependencies, CPAN modules included, can be obtained
> > > from the EPEL and RPMForge repositories. If the project is going to
> > > support RHEL and CentOS only then providing a RPM could allow you to
> > > remove the requirement to run (and maintain) the perl libs install
> > > script.
> > >
> > > Still a bit more work to do, but I thought I would send it along
> > > before I get too far to find out if anyone has
> > > suggestions/comments/criticisms. :)
> > >
> > > You can see it here:
> > > https://github.com/cybera/rpmspecs/blob/master/vcl.spec
> > >
> > > Right now it creates 3 packages: a main doc package (just contains the
> > > sql files right now), a web package, and a management node package.
> > >
> > > One question I have is about the:
> > >
> > > use VMware::Vix::Simple;
> > > use VMware::Vix::API::Constants
> > >
> > > in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> > > with VCL and the official install docs don't ask to have them
> > > installed either. But the rpmbuild process picks those modules up as
> > > requirements.
> > >
> > > Thanks,
> > > Curtis.
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
>
> iEYEARECAAYFAk/x6aIACgkQV/LQcNdtPQMR2QCfaC+Z2pMsgSqzz9VF+TTtsvoy
> o6oAn04jjYZJqKL6Uq+2JjJiTVSwNzB+
> =1SdY
> -----END PGP SIGNATURE-----
>
>
Re: RPM-ing VCL 2.2.1
Posted by Everett Toews <ev...@cybera.ca>.
Great. I just created an issue for this at
https://issues.apache.org/jira/browse/VCL-602
Everett
On Mon, Jul 2, 2012 at 12:34 PM, Josh Thompson <jo...@ncsu.edu>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Everett,
>
> I'd definitely like to see rpms for installing VCL.
>
> Josh
>
> On Friday, June 29, 2012 9:24:03 AM Everett Toews wrote:
> > Does anyone on the VCL core dev team have an interest in this? Should we
> > create a JIRA issue for it?
> >
> > Regards,
> > Everett
> >
> > On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. <se...@gmail.com>
> wrote:
> > > Hi All,
> > >
> > > I've been working on an initial spec file for VCL 2.2.1. Currently I
> > > believe all the dependencies, CPAN modules included, can be obtained
> > > from the EPEL and RPMForge repositories. If the project is going to
> > > support RHEL and CentOS only then providing a RPM could allow you to
> > > remove the requirement to run (and maintain) the perl libs install
> > > script.
> > >
> > > Still a bit more work to do, but I thought I would send it along
> > > before I get too far to find out if anyone has
> > > suggestions/comments/criticisms. :)
> > >
> > > You can see it here:
> > > https://github.com/cybera/rpmspecs/blob/master/vcl.spec
> > >
> > > Right now it creates 3 packages: a main doc package (just contains the
> > > sql files right now), a web package, and a management node package.
> > >
> > > One question I have is about the:
> > >
> > > use VMware::Vix::Simple;
> > > use VMware::Vix::API::Constants
> > >
> > > in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> > > with VCL and the official install docs don't ask to have them
> > > installed either. But the rpmbuild process picks those modules up as
> > > requirements.
> > >
> > > Thanks,
> > > Curtis.
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
>
> iEYEARECAAYFAk/x6aIACgkQV/LQcNdtPQMR2QCfaC+Z2pMsgSqzz9VF+TTtsvoy
> o6oAn04jjYZJqKL6Uq+2JjJiTVSwNzB+
> =1SdY
> -----END PGP SIGNATURE-----
>
>
Re: RPM-ing VCL 2.2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Everett,
I'd definitely like to see rpms for installing VCL.
Josh
On Friday, June 29, 2012 9:24:03 AM Everett Toews wrote:
> Does anyone on the VCL core dev team have an interest in this? Should we
> create a JIRA issue for it?
>
> Regards,
> Everett
>
> On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. <se...@gmail.com> wrote:
> > Hi All,
> >
> > I've been working on an initial spec file for VCL 2.2.1. Currently I
> > believe all the dependencies, CPAN modules included, can be obtained
> > from the EPEL and RPMForge repositories. If the project is going to
> > support RHEL and CentOS only then providing a RPM could allow you to
> > remove the requirement to run (and maintain) the perl libs install
> > script.
> >
> > Still a bit more work to do, but I thought I would send it along
> > before I get too far to find out if anyone has
> > suggestions/comments/criticisms. :)
> >
> > You can see it here:
> > https://github.com/cybera/rpmspecs/blob/master/vcl.spec
> >
> > Right now it creates 3 packages: a main doc package (just contains the
> > sql files right now), a web package, and a management node package.
> >
> > One question I have is about the:
> >
> > use VMware::Vix::Simple;
> > use VMware::Vix::API::Constants
> >
> > in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> > with VCL and the official install docs don't ask to have them
> > installed either. But the rpmbuild process picks those modules up as
> > requirements.
> >
> > Thanks,
> > Curtis.
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk/x6aIACgkQV/LQcNdtPQMR2QCfaC+Z2pMsgSqzz9VF+TTtsvoy
o6oAn04jjYZJqKL6Uq+2JjJiTVSwNzB+
=1SdY
-----END PGP SIGNATURE-----
Re: RPM-ing VCL 2.2.1
Posted by Larry Burton <la...@runningcedar.com>.
Hi Curtis,
You can do almost anything you wish in an RPM. My goal is to have a
one-click VCL installation for basic first-time users. Your suggestions
are appreciated.
Larry
Curtis C. wrote:
> On Fri, Jun 29, 2012 at 12:31 PM, Larry W Burton <lw...@ncat.edu> wrote:
>
>> Hi Everett,
>> Have you looked at the automated installation scripts I posted? They are set
>> up for inclusion in an rpm.
>>
>
> Hi Larry,
>
> I did come across your scripts on the wiki.
>
> At this point I was just using the official tar ball and the patch
> that is in the official instructions.
>
> Usually, AFAIK, RPMs only install the software and it's basic default
> configuration files. Once the package is installed then you could
> configure/initialize it with something like chef, puppet, ansible,
> etc, or your custom scripts.
>
> Thanks,
> Curtis.
>
>
>> Larry
>>
>> Dr. Larry Burton
>> Associate Professor
>> Department of Electronics, Computers, and Information Technology
>> School of Technology
>> North Carolina Agricultural and Technical State University
>>
>> -----Everett Toews <ev...@cybera.ca> wrote: -----
>>
>> To: vcl-user@incubator.apache.org, vcl-dev@incubator.apache.org
>> From: Everett Toews <ev...@cybera.ca>
>> Date: 06/29/2012 11:24AM
>> Subject: Re: RPM-ing VCL 2.2.1
>>
>>
>> Does anyone on the VCL core dev team have an interest in this? Should we
>> create a JIRA issue for it?
>>
>> Regards,
>> Everett
>>
>> On Mon, Jun 25, 2012 at 5:00 PM, Curtis C.
>> <
>> serverascode@gmail.com
>>
>> wrote:
>>
>> Hi All,
>>
>>
>> I've been working on an initial spec file for VCL 2.2.1. Currently I
>>
>> believe all the dependencies, CPAN modules included, can be obtained
>>
>> from the EPEL and RPMForge repositories. If the project is going to
>>
>> support RHEL and CentOS only then providing a RPM could allow you to
>>
>> remove the requirement to run (and maintain) the perl libs install
>>
>> script.
>>
>>
>> Still a bit more work to do, but I thought I would send it along
>>
>> before I get too far to find out if anyone has
>>
>> suggestions/comments/criticisms. :)
>>
>>
>> You can see it here:
>> https://github.com/cybera/rpmspecs/blob/master/vcl.spec
>>
>>
>>
>> Right now it creates 3 packages: a main doc package (just contains the
>>
>> sql files right now), a web package, and a management node package.
>>
>>
>> One question I have is about the:
>>
>>
>> use VMware::Vix::Simple;
>>
>> use VMware::Vix::API::Constants
>>
>>
>> in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
>>
>> with VCL and the official install docs don't ask to have them
>>
>> installed either. But the rpmbuild process picks those modules up as
>>
>> requirements.
>>
>>
>> Thanks,
>>
>> Curtis.
>>
>>
>>
>>
>> NOTICE: This e-mail correspondence is subject to Public Records Law and may
>> be disclosed to third parties.
>>
Re: RPM-ing VCL 2.2.1
Posted by "Curtis C." <se...@gmail.com>.
On Fri, Jun 29, 2012 at 12:31 PM, Larry W Burton <lw...@ncat.edu> wrote:
> Hi Everett,
> Have you looked at the automated installation scripts I posted? They are set
> up for inclusion in an rpm.
Hi Larry,
I did come across your scripts on the wiki.
At this point I was just using the official tar ball and the patch
that is in the official instructions.
Usually, AFAIK, RPMs only install the software and it's basic default
configuration files. Once the package is installed then you could
configure/initialize it with something like chef, puppet, ansible,
etc, or your custom scripts.
Thanks,
Curtis.
> Larry
>
> Dr. Larry Burton
> Associate Professor
> Department of Electronics, Computers, and Information Technology
> School of Technology
> North Carolina Agricultural and Technical State University
>
> -----Everett Toews <ev...@cybera.ca> wrote: -----
>
> To: vcl-user@incubator.apache.org, vcl-dev@incubator.apache.org
> From: Everett Toews <ev...@cybera.ca>
> Date: 06/29/2012 11:24AM
> Subject: Re: RPM-ing VCL 2.2.1
>
>
> Does anyone on the VCL core dev team have an interest in this? Should we
> create a JIRA issue for it?
>
> Regards,
> Everett
>
> On Mon, Jun 25, 2012 at 5:00 PM, Curtis C.
> <
> serverascode@gmail.com
>>
> wrote:
>
> Hi All,
>
>
> I've been working on an initial spec file for VCL 2.2.1. Currently I
>
> believe all the dependencies, CPAN modules included, can be obtained
>
> from the EPEL and RPMForge repositories. If the project is going to
>
> support RHEL and CentOS only then providing a RPM could allow you to
>
> remove the requirement to run (and maintain) the perl libs install
>
> script.
>
>
> Still a bit more work to do, but I thought I would send it along
>
> before I get too far to find out if anyone has
>
> suggestions/comments/criticisms. :)
>
>
> You can see it here:
> https://github.com/cybera/rpmspecs/blob/master/vcl.spec
>
>
>
> Right now it creates 3 packages: a main doc package (just contains the
>
> sql files right now), a web package, and a management node package.
>
>
> One question I have is about the:
>
>
> use VMware::Vix::Simple;
>
> use VMware::Vix::API::Constants
>
>
> in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
>
> with VCL and the official install docs don't ask to have them
>
> installed either. But the rpmbuild process picks those modules up as
>
> requirements.
>
>
> Thanks,
>
> Curtis.
>
>
>
>
> NOTICE: This e-mail correspondence is subject to Public Records Law and may
> be disclosed to third parties.
Re: RPM-ing VCL 2.2.1
Posted by Larry W Burton <lw...@ncat.edu>.
Hi Everett,
Have you looked at the automated installation scripts I posted? They are
set up for inclusion in an rpm.
Larry
Dr. Larry Burton
Associate Professor
Department of Electronics, Computers, and Information Technology
School of Technology
North Carolina Agricultural and Technical State University
-----Everett Toews <ev...@cybera.ca> wrote: -----
To: vcl-user@incubator.apache.org, vcl-dev@incubator.apache.org
From: Everett Toews <ev...@cybera.ca>
Date: 06/29/2012 11:24AM
Subject: Re: RPM-ing VCL 2.2.1
Does anyone on the VCL core dev team have an interest in this? Should we
create a JIRA issue for it?
Regards,
Everett
On Mon, Jun 25, 2012 at 5:00 PM, Curtis C.
<
serverascode@gmail.com
>
wrote:
Hi All,
I've been working on an initial spec file for VCL 2.2.1. Currently I
believe all the dependencies, CPAN modules included, can be obtained
from the EPEL and RPMForge repositories. If the project is going to
support RHEL and CentOS only then providing a RPM could allow you to
remove the requirement to run (and maintain) the perl libs install
script.
Still a bit more work to do, but I thought I would send it along
before I get too far to find out if anyone has
suggestions/comments/criticisms. :)
You can see it here:
https://github.com/cybera/rpmspecs/blob/master/vcl.spec
Right now it creates 3 packages: a main doc package (just contains the
sql files right now), a web package, and a management node package.
One question I have is about the:
use VMware::Vix::Simple;
use VMware::Vix::API::Constants
in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
with VCL and the official install docs don't ask to have them
installed either. But the rpmbuild process picks those modules up as
requirements.
Thanks,
Curtis.
NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties.
Re: RPM-ing VCL 2.2.1
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Everett,
I'd definitely like to see rpms for installing VCL.
Josh
On Friday, June 29, 2012 9:24:03 AM Everett Toews wrote:
> Does anyone on the VCL core dev team have an interest in this? Should we
> create a JIRA issue for it?
>
> Regards,
> Everett
>
> On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. <se...@gmail.com> wrote:
> > Hi All,
> >
> > I've been working on an initial spec file for VCL 2.2.1. Currently I
> > believe all the dependencies, CPAN modules included, can be obtained
> > from the EPEL and RPMForge repositories. If the project is going to
> > support RHEL and CentOS only then providing a RPM could allow you to
> > remove the requirement to run (and maintain) the perl libs install
> > script.
> >
> > Still a bit more work to do, but I thought I would send it along
> > before I get too far to find out if anyone has
> > suggestions/comments/criticisms. :)
> >
> > You can see it here:
> > https://github.com/cybera/rpmspecs/blob/master/vcl.spec
> >
> > Right now it creates 3 packages: a main doc package (just contains the
> > sql files right now), a web package, and a management node package.
> >
> > One question I have is about the:
> >
> > use VMware::Vix::Simple;
> > use VMware::Vix::API::Constants
> >
> > in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> > with VCL and the official install docs don't ask to have them
> > installed either. But the rpmbuild process picks those modules up as
> > requirements.
> >
> > Thanks,
> > Curtis.
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk/x6aIACgkQV/LQcNdtPQMR2QCfaC+Z2pMsgSqzz9VF+TTtsvoy
o6oAn04jjYZJqKL6Uq+2JjJiTVSwNzB+
=1SdY
-----END PGP SIGNATURE-----
Re: RPM-ing VCL 2.2.1
Posted by Everett Toews <ev...@cybera.ca>.
Does anyone on the VCL core dev team have an interest in this? Should we
create a JIRA issue for it?
Regards,
Everett
On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. <se...@gmail.com> wrote:
> Hi All,
>
> I've been working on an initial spec file for VCL 2.2.1. Currently I
> believe all the dependencies, CPAN modules included, can be obtained
> from the EPEL and RPMForge repositories. If the project is going to
> support RHEL and CentOS only then providing a RPM could allow you to
> remove the requirement to run (and maintain) the perl libs install
> script.
>
> Still a bit more work to do, but I thought I would send it along
> before I get too far to find out if anyone has
> suggestions/comments/criticisms. :)
>
> You can see it here:
> https://github.com/cybera/rpmspecs/blob/master/vcl.spec
>
> Right now it creates 3 packages: a main doc package (just contains the
> sql files right now), a web package, and a management node package.
>
> One question I have is about the:
>
> use VMware::Vix::Simple;
> use VMware::Vix::API::Constants
>
> in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> with VCL and the official install docs don't ask to have them
> installed either. But the rpmbuild process picks those modules up as
> requirements.
>
> Thanks,
> Curtis.
>
Re: RPM-ing VCL 2.2.1
Posted by Everett Toews <ev...@cybera.ca>.
Does anyone on the VCL core dev team have an interest in this? Should we
create a JIRA issue for it?
Regards,
Everett
On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. <se...@gmail.com> wrote:
> Hi All,
>
> I've been working on an initial spec file for VCL 2.2.1. Currently I
> believe all the dependencies, CPAN modules included, can be obtained
> from the EPEL and RPMForge repositories. If the project is going to
> support RHEL and CentOS only then providing a RPM could allow you to
> remove the requirement to run (and maintain) the perl libs install
> script.
>
> Still a bit more work to do, but I thought I would send it along
> before I get too far to find out if anyone has
> suggestions/comments/criticisms. :)
>
> You can see it here:
> https://github.com/cybera/rpmspecs/blob/master/vcl.spec
>
> Right now it creates 3 packages: a main doc package (just contains the
> sql files right now), a web package, and a management node package.
>
> One question I have is about the:
>
> use VMware::Vix::Simple;
> use VMware::Vix::API::Constants
>
> in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> with VCL and the official install docs don't ask to have them
> installed either. But the rpmbuild process picks those modules up as
> requirements.
>
> Thanks,
> Curtis.
>
Re: RPM-ing VCL 2.2.1
Posted by "Curtis C." <se...@gmail.com>.
On Fri, Jun 29, 2012 at 9:37 AM, Dmitri Chebotarov <dc...@gmu.edu> wrote:
>
> Curtis,
>
> I'm not sure if this can help - here a link to building VMware SDK's rpm -> http://www.firetooth.net/confluence/display/public/vSphere+Perl+SDK+and+CLI+RPM+Packages.
> Maybe VMware SDK rpm can be included as 4th package ...
Thanks Dmitri, I'll take a look. That might meet the dependency.
That said, installing that rpm is not part of the official
instructions so for most people that particular library will not be
available. :)
Thanks,
Curtis.
>
> Thanks.
>
> On Jun 25, 2012, at 19:00 , Curtis C. wrote:
>
>> Hi All,
>>
>> I've been working on an initial spec file for VCL 2.2.1. Currently I
>> believe all the dependencies, CPAN modules included, can be obtained
>> from the EPEL and RPMForge repositories. If the project is going to
>> support RHEL and CentOS only then providing a RPM could allow you to
>> remove the requirement to run (and maintain) the perl libs install
>> script.
>>
>> Still a bit more work to do, but I thought I would send it along
>> before I get too far to find out if anyone has
>> suggestions/comments/criticisms. :)
>>
>> You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec
>>
>> Right now it creates 3 packages: a main doc package (just contains the
>> sql files right now), a web package, and a management node package.
>>
>> One question I have is about the:
>>
>> use VMware::Vix::Simple;
>> use VMware::Vix::API::Constants
>>
>> in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
>> with VCL and the official install docs don't ask to have them
>> installed either. But the rpmbuild process picks those modules up as
>> requirements.
>>
>> Thanks,
>> Curtis.
>
>
>
> --
> Thank you,
>
> Dmitri Chebotarov
> Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
> 223 Aquia Building, Ffx, MSN: 1B5
> Phone: (703) 993-6175
> Fax: (703) 993-3404
>
Re: RPM-ing VCL 2.2.1
Posted by Dmitri Chebotarov <dc...@gmu.edu>.
Curtis,
I'm not sure if this can help - here a link to building VMware SDK's rpm -> http://www.firetooth.net/confluence/display/public/vSphere+Perl+SDK+and+CLI+RPM+Packages.
Maybe VMware SDK rpm can be included as 4th package ...
Thanks.
On Jun 25, 2012, at 19:00 , Curtis C. wrote:
> Hi All,
>
> I've been working on an initial spec file for VCL 2.2.1. Currently I
> believe all the dependencies, CPAN modules included, can be obtained
> from the EPEL and RPMForge repositories. If the project is going to
> support RHEL and CentOS only then providing a RPM could allow you to
> remove the requirement to run (and maintain) the perl libs install
> script.
>
> Still a bit more work to do, but I thought I would send it along
> before I get too far to find out if anyone has
> suggestions/comments/criticisms. :)
>
> You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec
>
> Right now it creates 3 packages: a main doc package (just contains the
> sql files right now), a web package, and a management node package.
>
> One question I have is about the:
>
> use VMware::Vix::Simple;
> use VMware::Vix::API::Constants
>
> in the VIX_API.pm file. Those libraries are not, AFAIK, distributed
> with VCL and the official install docs don't ask to have them
> installed either. But the rpmbuild process picks those modules up as
> requirements.
>
> Thanks,
> Curtis.
--
Thank you,
Dmitri Chebotarov
Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175
Fax: (703) 993-3404