MailScanner, CentOS 5 and perl-IO & perl-File-Temp

[Julian Field]

On 11/4/09 17:59, Mark Nienberg wrote:
> Julian Field wrote:
>>   the fact that RedHat got the module path @INC totally wrong in 
>> their release of Perl in RHEL 5, with the result that a lot of 
>> modules simply cannot be over-ridden without doing a "forced" install 
>> of files to overwrite stuff in their RPM, unless of course you mess 
>> with @INC at the start of your Perl program (which is what I have 
>> done) so that the vendor and site-specific directories actually get 
>> consulted before the core Perl system directories.
>>
> I think this ordering for @INC has always been the case on RHEL.  They 
> see it as a way to force the use of the supported versions of modules 
> instead of unsupported ones the user might have added.
> https://bugzilla.redhat.com/show_bug.cgi?id=124443
Yuck! It means you can't use more recent versions of Perl modules than 
the ones they supply, so you have to wait until they choose to upgrade 
you, if they ever do. Specifically stopping you using more recent stuff 
if you want to sounds like a particularly bad move to me. But I don't 
have to take their tech support calls.
>
> That said, I like what you are doing!  What about the perl modules 
> installed with your SA easy installer?  Can those eventually be done 
> the same way?
They aren't done via RPMs, but I guess I could. It would take a while 
though, and there has never been the demand to in the past.

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.