Re: Testing for a module's presence

Replies are listed 'Best First'.
Re^2: Testing for a module's presence by DrHyde (Prior) on Feb 07, 2005 at 10:53 UTC
This assumes that you only install modules using your OSes packaging system.	[reply]
Re^3: Testing for a module's presence by jpk236 (Monk) on Feb 07, 2005 at 14:54 UTC
Why wouldn't you want to? That's the beauty of FreeBSD. Justin	[reply]
Re^4: Testing for a module's presence by ehdonhon (Curate) on Feb 07, 2005 at 19:12 UTC
FreeBSD doesn't support every module ever written, and it certainly wouldn't support modules that the user has authored himself. Plus, if you install from FreeBSD ports, you are limited to using the version of Perl that FreeBSD is presently supporting. I really enjoy the power and beauty of the FreeBSD ports system, and use it very often. However, when it comes to CPAN.pm, it has its own beauty that often outshines even the ports system.	[reply]
Re^5: Testing for a module's presence by jpk236 (Monk) on Feb 07, 2005 at 20:24 UTC
Re^4: Testing for a module's presence by sth (Priest) on Feb 07, 2005 at 20:27 UTC
I allow the ports to install the Perl Ports that they depend on, but I always compile my own version of Perl. I have a Cpan script that install modules that I need and set config for Cpan. This way I don't have to go to each port and install the modules. I have another script that takes the perl tar file and installs it in /usr/local/perl-?.?? dir, links /usr/local/perl to the new perl dir and then runs the Cpan script to set the config and install the modules. The Cpan config is set to "follow" all dependent modules. I find this much more convenient than using all the ports, which use the BSDpan module.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks