Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Introducing Perlanet 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I tried to install this today on a personal hosting account today on a shared system where I have SSH access, but did not want to install the dependencies as root.

    First, I tried several alternatives for using PAR, building a packed file on my Linux laptop and uploading to the FreeBSD server. That failed in part because PAR failed to detect all the dependencies, including some of the XML::Feed namespace modules and some of the DateTime modules. It was also overly conservative about which modules it through needed to be platform-specific, so it claimed not to find some modules on the FreeBSD server, even though they were pure-Perl and already included in the PAR file, but in a Linux specific directory. I believe all the XS modules I needed were already installed on the FreeBSD server, so in theory this PAR approach could have worked.

    So using PAR failed, even with a fair bit of fussing.

    They I tried the private CPAN directory [perlmonks.org] option, which eventually failed fatally because my version of "libxml" was older than it wanted for XML::LibXML.

    Of course, using root access it would be easy, but I'll suggest from this experience that the dependency chain of XML::Feed is similar in complexity to that of Plagger from this perspective.

    To make this truly easy to use, I think it would need to be distributed with something like a multi-platform PAR file that has been pre-built on Linux, FreeBSD, etc.

    This isn't really a plagger-vs-perlanet issue, it's a problem with deploying Perl applications [perlmonks.org] in general.

    • I'll suggest from this experience that the dependency chain of XML::Feed is similar in complexity to that of Plagger from this perspective

      The dependencies checker indicates that XML::Feed has a 44% chance [cantrell.org.uk] of installing correctly whereas Plagger has a 26% chance [cantrell.org.uk]. Of course, Plagger uses XML::Feed so Plagger never going to be easier to install than XML::Feed.

      I had exactly the same problem with XML::LibXML that you did. My server is a Fedora Core 6 system and I install all of my modules using rpm (buildi

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.