bart has asked for the wisdom of the Perl Monks concerning the following question:

When I tried to use PPM to install demerphq's Data::Dump::Streamer from Podmaster's repository in ActivePerl 5.8.4, it aborted the installation with an error message that it couldn't find a PPD file Data-Dumper.ppd at the same repository. WTF, why would it even want that?

demerphq's module wants a copy of a recent version of Data::Dumper, to do some tests. In fact, his dependencies (URL is Makefile.PL for the same version of DDS) list a dependency on Data::Dumper version 2.121. The version I have on this perl is... 2.121. So why would it even actually want to update a module that is recent enough?

So I downloaded both the .ppd and the .tar.gz file, and tried a local install, after editing the PPD file to requiring a lower version of Data::Dumper. Same error. In fact, even dropping the requirement for a minimal version, by changing the VERSION attribute to "0,0,0,0", didn't fix it. The only thing that did work, was dropping the dependency on Data::Dumper from the PPD file entirely.

What is going on? Why does PPM refuse to acknowledge that Data::Dumper is actually already installed?

p.s. Changing the name of the dependency from "Data-Dumper" to "Data::Dumper" didn't help.

  • Comment on PPM fails to update a module that didn't even need updating

Replies are listed 'Best First'.
Re: PPM fails to update a module that didn't even need updating
by PodMaster (Abbot) on Nov 11, 2004 at 07:48 UTC
    FYI, there is a force option (so says the manual).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.