Michael Cummings wrote:
> Just posting a link to my blog so that the non-freaks (those who don't
> read my blog) have a chance to complain :) This 'article' explains what
> i've been doing with my experiment in slotting perl, mixing threaded and
> non-threaded perl, etc.
>
> http://www.datanode.net/?p=153
>   

Ooh, you're slotting perl? :)
I recall a conversation where I suggested slotted perl and you told me 
it's nearly impossible... :-)
I just have to quote you on this one: "it's always been my opinion that 
it would be far more trouble than its worth" (sorry! had to!).
So I'll start by saying I'm REALLY glad you're experimenting with it.

You ended that conversation suggesting we'd move it to 
gentoo-perl@g.o.
So let's:

I didn't think about having both threaded and non-threaded perl (but 
this could be so cool...), only different versions of perl.
A few things I've been thinking about:

   - What exactly happens when someone emerges a dev-perl/* ebuild..? 
Will it be installed for each perl version? Shared between all perl 
versions (might cause problems)?

   - Every module's ebuild should know what perls it can run under...

   - ..."After emerging Test-Harness, 2.56 stays at the top of the stack 
at all times" is nice, but think of situations when the newer version of 
a module can't work with older versions of perl. OUCH.

  - I'd personally like the ability to emerge a module for a specific 
version of perl. Since each perl version has its own Config.pm, each 
perl could have its own @INC, and possibly a "shared" lib between all perls.

Just my $.02...

  --Yuval

-- 
gentoo-perl@g.o mailing list