Hi Ben, answers inline...
On 03/21/2010 10:01 PM, Ben DJ wrote:
If I configure a build of openca-base as,
./configure ... --with-build-dir=$OPENCA_BUILD_DIR
--with-module-prefix=$OPENCA_MODULE_DIR ...
perl modules are installed under,
$OPENCA_BUILD_DIR/OPENCA_MODULE_DIR/perl5/OpenCA/BLAH.pm
notice the prefixing of an ADDITIONAL ".../perl5/..." to the module's path.
It is not an ADDITIONAL - the perl5 is standard directory (for perl 5.x.x). The module dir allows you to specify different installation directories, not really used by anybody AFAIK. NOTE that the BUILD directory is only for creating packaging (e.g, RPMs) and you should not use it otherwise...
If, instead, I install an OpenCA module via 'cpanp', e.g.
module_info OpenCA::TRIStateCGI
Can't create Module::Info object for module
'OpenCA::TRIStateCGI' at
/usr/bin/module_info line 96.
cpanp -i OpenCA::TRIStateCGI
module_info OpenCA::TRIStateCGI
The CPAN versions of the modules are outdated at the moment, do not use them.
it's installed @,
Name: OpenCA::TRIStateCGI
Version: 1.5.5
Directory: /usr/lib/perl5/site_perl/5.10.0
File: /usr/lib/perl5/site_perl/5.10.0/OpenCA/TRIStateCGI.pm
Core module: no
That is the default installation dir for your PERL modules. It's the system wide directory. If you do not need the OpenCA modules outside OpenCA, I would suggest not to use the standard directory. Also, this allows you to update your system-wide PERL installation/modules without affecting OpenCA.
where my installed perl has,
perl -V | grep "@INC" -A10
@INC:
/usr/lib/perl5/5.10.0/x86_64-linux-thread-multi
/usr/lib/perl5/5.10.0
/usr/lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi
--> /usr/lib/perl5/site_perl/5.10.0
/usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.10.0
/usr/lib/perl5/vendor_perl
.
If I'm going to install the perl-modules via the openca-base build&
install, shouldn't the modules be installed under "
/usr/lib/perl5/site_perl/5.10.0/OpenCA/", like the cpan install would
do?
You can install openca as "system-wide" program by using:
$ ./configure --prefix=/usr --with-module-prefix=""
Again, I *strongly* suggest you do not install the modules in the default
installation directory. This allows you also to uninstall the OpenCA installed
module without affecting other applications.
Shared modules are great, but can really be a pain...
Cheers,
Max
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
