Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 21751 - perl 5.8.0 masked
Summary: perl 5.8.0 masked
Status: VERIFIED LATER
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-27 02:25 UTC by Alex Buell
Modified: 2011-10-30 22:21 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Buell 2003-05-27 02:25:49 UTC
default-1.0 has perl restricted to perl 5.6. Should this be changed to allow
perl 5.8 to be used?
Comment 1 Robert Coie (RETIRED) gentoo-dev 2003-05-28 04:17:27 UTC
There are still some architectures that have not declared 5.8 stable.
Comment 2 Alex Buell 2003-05-28 10:20:12 UTC
x86 looks stable enough to me.
Comment 3 Michael Cummings (RETIRED) gentoo-dev 2003-06-02 06:02:44 UTC
Let's confirm we have an upgrade schema before unmasking for default-1.0. The last time we unmasked for the 1.4's, it was a nightmare.
Comment 4 Gentoo Perl team gentoo-dev 2003-06-10 04:15:21 UTC
Keep this locked for now.
Comment 5 Alex Buell 2003-06-10 04:27:42 UTC
Fair enough. I decided to upgrade the 1.2 gentoo box to 1.4 instead of waiting. IMHO, it's the best way to get Perl 5.8.0. 
Comment 6 Gentoo Perl team gentoo-dev 2003-06-10 04:41:24 UTC
The real issue here is having a clean way to *complete* the upgrade. There is the libperl_rebuilder, which is really just a hack attempt at isolating installed components that use the old libperl.so, as well as perl modules, and re-emerge them. Until there is a smooth way to upgrade without inflicting damage (libperl_rebuilder is decent, but it has its hickups) I think we should keep this locked. 

And a clean box always wins :)
Comment 7 Michael Cummings (RETIRED) gentoo-dev 2005-07-18 03:06:42 UTC
Since 5.8.6 is now the current stable, going to go ahead and mark this lost bug
as closed :)