I see there's a DPKG-Tools package on CPAN. Maybe your module would fit nicely inside that package? It seems that your module would be most useful to those people that already handle dpkgs anyway.
Another idea would be to put it into the Archive:: namespace, which is already well-established. E.g.
- Archive::dpkg::ParseControl
- Archive::Debian::ParseControl
- Archive::dpkg::ControlFile
- Archive::Debian::ControlFile
I find it nicer to flesh out existing (and fitting, of course) namespaces rather than creating new ones.
Update: By the way, I don't find it so necessary to have "Parse" in the name. Many Perl modules do parsing, and most of the time it is just enough to name the thing that your module is dealing with (in this case: control files). It is implied that you parse those files in order to read/write them :).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.