Bug 59986 - When will there be an errata for 7.x to update to Perl 5.6.1??
Summary: When will there be an errata for 7.x to update to Perl 5.6.1??
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: perl
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-18 05:07 UTC by Oliver Jones
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-02-18 05:07:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Oliver Jones 2002-02-18 05:07:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
It is pretty common knowledge that Perl 5.6.0 is not very stable when it comes 
to eval's.  For example the HTML::Mason template engine doesn't like 5.6.0 very 
much.  When will there be a RPM errata released to upgrade 7.x to Perl 5.6.1??

This is important to me.  

Is it safe to just use the 5.6.1 rpm from RawHide?

Comment 1 Chip Turner 2002-02-18 20:33:41 UTC
It is safe to use Rawhide's Perl, but you will need to edit the spec file
(search it for "rawhide").  If you don't, you will get a perl that is not binary
compatible with your installed modules. For an equally unsupported approach,
though probably maintaining binary compatibility, you can get RPMs from:

http://people.redhat.com/cturner/perl/

They should work, but there are no guarantees.


Comment 2 Oliver Jones 2002-02-19 00:31:13 UTC
If by editing the SPEC you mean changing the %define build_8x 1 to 0 then I did
that already.  If not then please advise what changes I need to make.

Thank you.

Comment 3 Oliver Jones 2002-02-19 00:34:47 UTC
Oh and also, I don't use the binary rpm perl modules.  I tend to use CPAN for
obtaining perl modules. And I'll probably rebuild things like ImageMagick (which
has a perl interface) etc from SRPMs also.


Note You need to log in before you can comment on or make changes to this bug.