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).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||