This is a great start -- though a bit of a quick-start at that, as it's more of a description of what happens than a guide for what to do. Here are some suggestions for where to go next:
Distinguish between "ordinary user" installs and "root" installs -- the decisions for some options are often quite different. (e.g. PREFIX). You might want to lay out the scenarios at the start and then refer to them as you go. Have one entry for each option -- right now, the text blurs many of them together. Provide some recommendations and rationale (or pros/cons) of different choices. E.g. why "follow" prerequisites versus "ask". This will be more helpful than just a description of the different choices. Describe how to manually tweak options afterwards with "o conf option" and "o conf commit".
If you expand this guide, consider writing it in Pod and submitting it to Andreas Konig (the CPAN maintainer). Perhaps it can be included in a future release.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
-
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.
|
