I don't know about package the dependent modules, but if you're installing each dependent module manually (having first downloaded it) you can use the PREFIX macro to specify an alternative installation directory when generating the make script e.g. perl Makefile.PL PERFIX=path/to/some/other/dir, and then subsequently i.e. run-time, use PERL5LIB to point to that same alternative directory.

It would appear that the above installation behaviour can be emulated when using CPAN driven installation by utilising the makepl_arg CPAN config option - but never having used this option, I can't vouch for it...

A user level that continues to overstate my experience :-))

In reply to Re: Question: Best practices for packaging scripts by Bloodnok
in thread Question: Best practices for packaging scripts by jujiro_eb

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.