Tim Donahue <[EMAIL PROTECTED]> wrote: > In my experience since stuff in CPAN generally "Just Works"(TM) on > OpenBSD and is as simple as `perl -MCPAN - e "install <module>"` I > really can't see any compelling reasons for everything to be put into > the ports tree.
As you say, CPAN itself works fine independently. But one possible improvement would be to add some integration between the ports/package system and Perl's default @INC paths (which includes modules installed with /usr/bin/cpan, and those installed manually via "perl Makefile.PL"). Right now, if package foo depends on p5-bar-baz, the package system first checks the list of installed packages and then your $PKG_PATH (and possibly the ports tree if you're installing via ports). But if you happen to already have installed Bar::Baz with cpan, it doesn't detect that... I don't know of any OS that has this kind of integration. The closest equivalent might be Debian's dh-make-perl which allows you to take a CPAN module tarball and create a .deb file out of it, which you then install as you would any other package. But that's still an extra step. One point I forgot to mention ealier to the OP: another nice thing about Perl is that it comes in the base system. All other languages you mentioned have to be installed via packages/ports. -- Stephen Takacs <[EMAIL PROTECTED]> http://perlguru.net/ 4149 FD56 D078 C988 9027 1EB4 04CC F80F 72CB 09DA
