I've been writing in Perl for years, but I've never released anything to CPAN before.

Now though, I have a bulk rename program that I've been working on, and its nearing the point where I'd like to upload it to CPAN. The big question is what naming hierarchy to use.

I haven't been able to find a FAQ for what the various top-level names in CPAN are for, and the only relevant info I could find in the CPAN FAQs says:

"Please, talk to other people (comp.lang.perl.modules, modules@perl.org or any mailing list that fits your problem domain) before you decide upon the namespace you're going to use for your module."

This doesn't help me much as I haven't had access to usenet for years, and modules@perl.org doesn't appear to be a discussion community. I figured I could ask here about my naming ideas, and you could point me to any better place that I should be asking my questions.

The program itself is a bulk rename utility that was originally based on File::Rename but has now morphed into a completely different beast. It seems that that the App top-level namespace is intended for stand-alone applications, so I've been thinking of uploading it as App::BulkRename or maybe App::FileTools::BulkRename, as there are other related file manipulation tools I may want to release later.

On the other hand, as a distant fork of File::Rename, I suppose that one might also consider uploading it as File::BulkRename but I wonder if that wouldn't confuse folks into thinking its a bulk rename library, as opposed to a stand-alone program.

I also considered uploading it to CPAN scripts, but they seem to demand one-file scripts, and this program already consists of a number of modules and a data file.

Anyway, any advice on naming this thing would be appreciated.

In reply to Standalone Script Naming for CPAN by swestrup

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.