The author of this module listed a copyright date as of 2002 and nothing about the GPL and he uploaded it to CPAN. Given that everyone understands to place it CPAN means that it will be distributed to CPAN source nodes, he was OK with that method of distribution.
As for whether you can distribute it yourself on a CD, well, that is something else. The reason is that the author could never change his mind and stop distributing it. At least with CPAN, if he wishes, he can turn around and say that this is no longer accessible(whether this is practical is an exercise for the reader...).
As Corion pointed out, perhaps you would be better off reimplementing the module on your own since it is fairly small and would be easier to do than argue with a bunch of lawyers.
As for dual licensing, it allows a customer who wants code changed and does not want those changes distributed (for whatever reason). The dual license gives the author a private version for clients and a public version(GPL) for everyone else.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||