My vote goes to option 2. It might be hard to find initially, but both the user and the software will always know where it is (after they find it once).
I don't like option 1 because I don't see it as being very portable. I don't like option 3 because it introduces the possibility of user error (typo, etc) during install, and it's more of a pain to install. I like no-fuss, no-muss installations and I'm sure I'm not alone. I actually don't mind option 4 very much, but it seems that's not your favorite. Option 5 I think is the worst solution, as you don't want to keep changing the module source just for a config change. Not only is that a big problem if your module gets released into the wild, but also it introduces the possibility of inadvertantly creating syntax errors in the code.
It's all fine and dandy until someone has to look at the code.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||