Re^3: Move Perl modules to new CentOS VPS

in reply to Re^2: Move Perl modules to new CentOS VPS
in thread Move Perl modules to new CentOS VPS

Greetings,

Should be a no brainer. You have root. So just fire up what ever flavor of application management your flavor of Linux uses -- yum, druid, slac, apt, ... and take inventory. Is GD installed? Was the package the "development" version (you'll probably want that one) while I run *BSD's. As I recall, getting all the optional libraries often wanted on a Linux box required the development packages. Anyway. If you perform this step ahead of your localized Perl install/upgrade. You shouldn't run into any difficulties that aren't easily handled.

HTH

--Chris

#!/usr/bin/perl -Tw
use Perl::Always or die;
my $perl_version = (5.12.5);
print $perl_version;

Comment on Re^3: Move Perl modules to new CentOS VPS

Replies are listed 'Best First'.
Re^4: Move Perl modules to new CentOS VPS by Anonymous Monk on Nov 09, 2013 at 11:20 UTC
FreeBSD is my personal OS `;->` (where headers & libraries are generally installed together). I ever so mildly get annoyed with prebuilt packages (installed via rpm\|yum) on GNU/Linux whenever I have to install "x-devel" package for install of "x" package alone omits related header files. (So, does anybody know of the secret password that would install libraries and headers while installing "x" alone (short of a wrapper script)?)	[reply]

Replies are listed 'Best First'.

Re^4: Move Perl modules to new CentOS VPS
by Anonymous Monk on Nov 09, 2013 at 11:20 UTC

FreeBSD is my personal OS ;-> (where headers & libraries are generally installed together).

I ever so mildly get annoyed with prebuilt packages (installed via rpm|yum) on GNU/Linux whenever I have to install "x-devel" package for install of "x" package alone omits related header files. (So, does anybody know of the secret password that would install libraries and headers while installing "x" alone (short of a wrapper script)?)

[reply]

In Section Seekers of Perl Wisdom