I think you've hit the nail on the head. I wouldn't use freshmeat for pure modules. As a user, I always search for modules on CPAN first, then google/freshmeat etc. On the other hand, I do use freshmeat to search for applications, especially if I don't really care what language they're written in, and I hardly ever use CPAN for that. So if you're writing a stand-alone application, freshmeat (or sourceforge) is a pretty good option, IMO.

Well, indeed, to quote from Autrijus Tang's Perl 6 is Here Today: "CPAN is my programming language of choice; the rest is just syntax."

Now, I'm quite sure that this has been discussed here before: people tend to think that CPAN is or should be exclusively for modules. While I disagree with this point of view as long as it's the Comprehensive Perl Archive Network (no reference to modules whatsoever), I see a point for publishing whole applications elsewhere.

Most importantly I see no problem in publishing both at CPAN and on SF and/or FM. The different locations may be aimed at different target users, in particular perl developers for the former and "final users" for the latter ones.

In reply to Re^2: CPAN vs. Freshmeat by blazar
in thread CPAN vs. Freshmeat by b10m

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.