an rpm howto question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On 6/29/05 2:21 PM, Nielsen, Steve wrote:
> I am in a precarious spot....
> 
> I run centos 4.0. I upgraded my mod_perl RPM to mod_perl 2.0.1.
> CGI.pm 3.10 (3.05 comes with centos 4.0) fixes some namespace issues
> with mod_perl vs mod_perl 2.0.1. I need to upgrade to it to 3.10. Yet
> that file belongs to the perl rpm that comes with centos.
> 
> What do people generally do in this type of situation?

For Perl, I just do a complete build (hopefully scripted!) into 
/usr/local and manage it with CPAN. There are some packages, like RT, 
that require so many additional modules that it's just easier to 
maintain a local perl than it is to work with the system-installed 
version. So standard scripts can still reference /usr/bin/perl, but 
scripts with extensive local dependencies use /usr/local/bin/perl.

-- 
Paul Heinlein <> heinlein@xxxxxxxxxx <> www.madboa.com

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux