Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I want to be able to develop a perl (web) script containing both CPAN and personal modules on a development machine the upload the entire *package* to a shared hosting environment.

Often times I can't get various required modules built/installed on my host. (Generally using or building from source in my own lib directory) Most things I try to build die for some reason or another. This is probably my real problem, however after tinkering with Ruby on Rails I came across a sweet little feature called 'rake freeze_gems'. What this does is 'freeze' your gems (modules) by copying them into a .vendor directory, thus allowing you to upload the entire working app to a shared host.

Is there a Perl equivalent? Something that will allow me to bundle all of a script's dependent modules into a new directory that I assume I'd have to push into @INC?

I've looked into PAR, but I have no experience with it. Also, I also assumed that this must be a common problem in shared hosting environments (or am I alone?) Is there a commonly accepted way to handle this problem?


Spread Firefox

In reply to Packaging dependent modules with Perl script(s) for shared hosting environments by silent11

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.