Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
If the code was legitimately released under an open license (which is, admittedly, a potentially-very-large "if"), then the open-licensed versions are out there and there's not much that can be done about it, as the license allows anyone who has the code to redistribute it, including putting it back onto CPAN. The owner can choose to release new versions only under closed licenses (or to not release them at all), but the cat's out of the bag on the open versions and the best you can do is to fork the code into separate open and closed versions.

If it wasn't legitimately placed under an open license, well... you may find yourself in need of a very good lawyer once they realize that you released code you didn't own and claimed that it was licensed under terms you weren't authorized to offer.

In reply to Re: Need arguments to keep my modules on CPAN by dsheroh
in thread Need arguments to keep my modules on CPAN by dk

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.