Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.
 
PerlMonks  

Re: CPAN - As Seen From Space!

by Anonymous Monk
on Dec 17, 2011 at 18:19 UTC ( [id://944098]=note: print w/replies, xml ) Need Help??


in reply to CPAN - As Seen From Space!

I tried to run it locally using contents of your github repo, as advised in the help section. However it does not seem to work as it tries to access files in the source_data directory, which is not in the repository. Can you add these files to the repository or maybe suggest how can I replace them?

Replies are listed 'Best First'.
Re^2: CPAN - As Seen From Space!
by grantm (Parson) on Dec 17, 2011 at 19:18 UTC

    Pulling the latest version from github should fix your problem. The source_data directory simply needs to exist. You could just create it if it's not there, but the latest version of the code should create it automatically.

    Having said that, it wouldn't surprise me if you encountered other issues. The code hasn't been widely distributed so it's like to have undeclared dependencies and non-portable assumptions in the code. By all means let me know of these so I can fix them. The github issue tracker is probably the best place to do that.

      Thanks, I have figured it out. Created source_data dir and put these files there:
      01mailrc.txt.gz 02packages.details.txt.gz all_ratings.csv
      Other things I had to change were minor, like lib path in the script and some nginx settings after they were written by puppet. Puppet also was unable to install 3 perl modules, which I then installed with cpan.

        When the script is run with the --refresh-data option it will download the latest version of those files.

        My personal preference on Debian/Ubuntu systems is to never install modules directly from CPAN. I use dh-make-perl to download the tarball, and build a .deb e.g.:

        dh-make-perl --build --cpan Math::PlanePath

        The .deb package can then be installed with dpkg or dropped into a repo. For a small hobby project like this it could be seen as overkill (although it's actually quick and easy). For bigger work-related projects it's invaluable to know that the same module version is being installed in dev, staging and production (rather than getting the latest version when you do your production rollout and getting a nasty surprise).

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://944098]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2024-03-29 06:34 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found