a collection of modules that are for building applications that access the NOAA Global Climatology Network data repository. I've named these modules GHCN::Station, GHCN::StationTable etc.

Forgive me, but that seems to be a rather specific use case. Why is it that you think this deserves its own top-level namespace? Wouldn't these fit under WebService:: or somewhere like that? Did you discuss the name here first? On or PrePAN? Or on module-authors@perl.org?

my .pl scripts, which I said reside under bin are listed as Documentation! Why?

Perhaps because scripts like this are usually placed in scripts/ as opposed to bin/?

To answer the question in the title, you should indeed split the dist into 2. People who want to use the webservice/protocol side of it won't necessarily want the application. So, distribute the webservice integration as one dist and the application as a second dist which has the first as a dependency.

While you're in there making such changes, it would be better to omit the dist.ini from the uploaded tarball(s).

Edit: Gah! PrePAN appears to have gone and been snaffled by a domain grabber. Another one bites the dust.

🦛

In reply to Re: How do I package a module and related apps for successful upload to cpan by hippo
in thread How do I package a module and related apps for successful upload to cpan by PUCKERING

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.