Is Perl 5.8.0 unmasked then?

alshain · Posted: Wed Dec 11, 2002 4:40 pm Post subject: Is Perl 5.8.0 unmasked then?

Well, doing an emerge -up world shows:

These are the packages that I would merge, in order.

Calculating world dependencies ...done!
[ebuild U ] sys-devel/perl-5.8.0-r3 [5.6.1-r7]

But looking at the ebuild shows:

KEYWORDS="~x86 ~sparc ~ppc ~alpha"

So it should be masked, right?! I'm using the stable profile.

Or could this be related to a strange going on where if an ebuild has the ~ removed then even if you add it again and/or rsync, it will still remain unmaked. I've noticed this before - is it just me?

Andrew

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

5.8 is still masked on my system. Do you have ACCEPT_KEYWORDS set for your shell env?
_________________
Quis separabit? Quo animo?

patrickfo · Posted: Wed Dec 11, 2002 4:51 pm Post subject: perl 5.8-r3 "~x86"

hello
on all perl -5.8-r3 "~x86"
on two of them update world => perl-5.8.0-r3
and on another perl-5.8.0-r2 ( which is "x86"
curious isn't it?

Lolo- · n00b Joined: 04 Aug 2002 Posts: 62 Location: SQY (France)

it depends on which rsync server you contacted ?

patrickfo · Posted: Wed Dec 11, 2002 5:16 pm Post subject: perl-5.8.0-r2

another emerge rsync and all are perl-5.8.0-r2
just a question of time?

alshain · Posted: Wed Dec 11, 2002 5:21 pm Post subject:

darktux · Posted: Wed Dec 11, 2002 5:41 pm Post subject:

doug-x07 · Posted: Wed Dec 11, 2002 7:44 pm Post subject:

I directly emerged the perl-5.8.0-r3.ebuild about a week back. Getting it to compile was fun, had a few segmentation faults but not sure if that was due to the ebuild or other gcc issues I had been having. I saw the post and ran emerge -up world --pretend after having rsynced , surprised by the output for perl

alshain · Posted: Wed Dec 11, 2002 8:09 pm Post subject:

Well, 5.8.0 is gone again now! Probably unmasked accidentally (twice).

I'm a bit relieved - 5.8.0 breaks virtually everything dependent on Perl. I upgraded to 5.8.0 when I was one with Mandrake and that was one of the many last straws that eventually convinced me to switch to Gentoo.

Andrew

Lockup · Guru Joined: 25 Jul 2002 Posts: 430

well earlier today i did an emerge -u world...which upgraded perl to 5.8.
now(a few hours later) an emerge -up world:

Lockup · Guru Joined: 25 Jul 2002 Posts: 430

oh....ill shut up and downgrade:

alshain · Posted: Wed Dec 11, 2002 9:21 pm Post subject:

lemming · n00b Joined: 07 Aug 2002 Posts: 57 Location: Kanab, UT

The thing to remember that any XS modules will need to be recompiled to work with 5.8 perl.

perldoc perldelta has the details.

Probably to be safe, you should re-emerge any Perl modules after innstalling 5.8.
_________________
-mark

asroka · Posted: Fri Dec 20, 2002 10:38 pm Post subject: build perl from the source

perl is actually really easy to build from the source. What I have done is build 5.8.0 from the source (not the ebuild) which by default puts it in /usr/local/bin and kept 5.6.1 installed as well which is in /opt or some such place. This way nothing that depends on perl breaks but I can still use the new features of 5.8 for development such as interpreter threads and the improved perl compiler, etc.

To build perl from the source get it from:
http://www.perl.com/CPAN-local/src/stable.tar.gz

then just run the following commands in the directory where you untarred it:

rm -f config.sh Policy.sh
sh Configure
make
make test
make install

If you want to use 5.8.0 by default at this point all you have to do is:
rm /usr/bin/perl
ln -s /usr/local/bin/perl /usr/bin/perl

However this might break scripts if they are dependent on 5.6.1 binary (XS) code and use /usr/bin/perl as the shebang

BTW, I did that last trick on a PIII 733 running Gentoo with Gnome and a whole bunch of apps and nothing broke (That I know of ;-)

However, I wasn't brave enough to do it to my server which uses the current portage versions of mod_perl and a bunch of other stuff. All depends on how dependent you are on perl for your day-to-day stuff.