in reply to Install Module issue

Seems like you have two versions of the module installed and perl is loading pieces of one and pieces of the other. I think ppm is intended to be used as a network installer and probably uses better magic that way.

Have you seen DB_File? I believe that comes with (active)perl.

If I needed the advanced features of 2.x+, then I would run ppm and "install BerkeleyDB" from the ppm shell. I'm pretty sure ppm even has a GUI now.

-Paul

Replies are listed 'Best First'.
Re^2: Install Module issue
by rodion (Chaplain) on Apr 30, 2007 at 11:44 UTC
    The command line version of "ppm" is still there if you want it, but it can be hard to find. You have to use "ppm-shell" now if you want to get to the non-GUI version. "ppm" by itself launches the GUI version, which takes some of your time waiting while it resynchronizes, and some of your thinking time as you adapt to the new interface. (Once you do adapt, it has some nice features, but a somewhat innovative "take" on its user interface, IMHO.)
[reply]
      The command line version of "ppm" is still there if you want it, but it can be hard to find

      Hmmm ... I just ran ppm install Win32-API in a fresh installation of the latest ActiveState build (820) and it installed just fine - thankfully without launching any GUI crap at all. This seems to be in contradiction to your post - or have I misunderstood something ?

      Cheers,
      Rob
[reply]
[d/l]

        The ppm shell still attaches to the win32 console, so you'll get a dos window either way (iirc). If you start ppm without any arguments, it'll pop up the GUI — unless you have an older version of active perl. If you have the latest build, then I suspect you gave it install arguments and it didn't bother with the GUI since it already knew what you wanted.

        P.S. Don't be too down on the GUI. It lowers the bar for new perl nerds and it's not a bad GUI at that.

        -Paul

[reply]

In Section Seekers of Perl Wisdom