If 2) depends on modules authors catering for Debian, I wouldn't use 2). We have all those lovely tools to make CPAN packages, and to download them so module authors do not have to care about the gazillion ways CPAN modules can be installed.
I'd go for 1) if Debian has made that easy. Solaris used to do this right (and probably still do, but I don't have access to a recent Solaris at the moment to verify). Solaris also has tools using Perl. /usr/bin/perl is a link to /usr/whatever/perl. Solaris specific tools start with #!/usr/whatever/perl. This means that if one doesn't install their own perl, one can use #!/usr/bin/perl (because a perl is there). But it also means one can install a /usr/bin/perl without breaking the system tools. If Debian does the same, I'd certainly go for 1). Otherwise, I probably would go for 3).
-
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.
|
