If you are willing to ship binaries, the usual answer would be: use PAR;. You can also install .par files into the local system using PAR::Dist. To solve the bootstrapping problem (no PAR::Dist on the target system), you can just include that (pure-Perl) module into the installer script. Then it requires either Compress::Zlib and Archive::Zip to be present or an "unzip" tool. ActiveState's Win32 perl includes those modules. Unix usually has an unzip. Perl 5.10 will always include Compress::Zlib and Archive::Zip is pure-Perl and thus it's possible to inline it into the installer script. For an example, check out the local-path-installer script I hacked up for bugzilla .
As for the problem of the original poster: You could check out Adam Kennedy's "pip" tool.
Cheers,
Steffen
-
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.
|
