Hi,
Further to CPAN's rendering of POD links (which deals with the incorrect rendering of the Inline::C-Cookbook pod weblink on CPAN), before I upload another bugfix version of Inline::C to CPAN, I'd like to check that the problem pod link is going to work correctly in the next release.
In order to do that, I would like to upload to CPAN some bogus/useless distro - a distro that does nothing other than verify that I've worked out how to deal with that problem with the pod weblink.

Is there a preferred namespace to use when uploading such "testing-the-water" distros to CPAN ? Is it ok to do this ? (Once I've verified that I've got it right, the bogus/useless distro will be removed from CPAN - but, I guess, will still be locatable on backpan.)

Cheers,
Rob

In reply to CPAN test facility by syphilis

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.