All the Perl that's Practical to Extract and Report

Ruby gets CPAN.pm

Matts on 2002-03-13T11:41:00

Or an equivalent of (perhaps better?) - based on debian's apt-get/dpkg. Rpkg

Sweet

djberg96 on 2002-03-13T13:40:48

Thanks for that post and link. AT&T Broadband dropped comp.lang.ruby from the list of available newsgroups recently for some reason, so my only link to that group is via deja, which I generally only use for searching archives.

I'm really very curious to see how much I'll be attached to Ruby after Perl 6 comes out. :)

Re:Sweet

gnat on 2002-03-13T14:54:54

I'm really very curious to see how much I'll be attached to Ruby after Perl 6 comes out.

My attitude is: if rapt is sweet, we'll steal it :-)

--Nat

You know, I didn't adopt Python because...

jdavidb on 2002-03-13T18:09:27

... I was told Python fixed all of Perl's faults, but when I looked the module system was banannas, and that was where I most wanted changes. (Don't get me wrong: Perl's system is great as is. I just thought the "innovative" Pythoners would have learned from Perl's "mistakes" and have a really slick system.)

Nat's right. If rapt/rpkg looks good, we steal it. Rewritten in Perl of course.

We need an ultraflexible apt-like module install system running over CPAN. Modules need to be self-contained tarballs that can be dropped into the Perl core unchanged to create custom distributions (almost there; too many interactive Makefile.PL's). It needs to be possible to install multiple versions of a module in a system identical to the way UNIX does shared libraries, similar to what I described elsewhere on this site about hardwiring all my programs to perl5.6.1.

But, I'm rambling. It's all IMHO. What we have now is spectacular. I'd like to see it even better.