Stick with cpan modules.
Delegate the responsibility of deps to whomever has root access on servers. That's how I roll. Similar situation.
I have a few very complicated doc maintenance type systems- all perl/bash- mostly perl- also CGI::Application head to toe for the gui.
Screw the install like wordpress- using cpan is easier. Btw, I love wordpress, I even install it for clients and friends. I just wget the source, tarxvf, and replace public_html with .. anyhow.. Comparing these things, it's like apples and organges. I say stick with perl/cpan the way it is, don't try to do clever tricks like prepackaging deps, etc. You'll shoot your eye out.
-
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.
|