If I write a complex application with perl- comprised of modules, executables, config files, web interface, cli interface, etc.

Should I put the modules on cpan (yes, they can be used by others, for other things) and- the executables on sourceforge, or some other website of its own?

I want to give one example. I have a collection of hacks that lets you organize paper bank checks. The application consists of

  1. module to understand the international MICR standards
  2. module to interact with ocr to find a MICR line in a check image
  3. cli executables, to read a check etc
  4. library of bitmaps to understand MICR images, this is the kind of thing that goes in /usr/share
  5. web interface to search checks by account number, examine misread MICR codes by ocr, etc.

It makes sense to me that the perl modules that can be of use in other apps and for other reasons, should go on cpan. What about the web interface files? I mean, the cgi files, config files. Should that go in its own project site, like bugzilla, or on sourceforge? Instead of anything on cpan.

What about the command line interface that uses a perl module.. Maybe that goes with the distro for cpan.

Any thoughts on this?

If the application interface were web based, I could see a simple argument for keeping the module libs alongside the cgi executables. This is what Bugzilla seems to do.

In reply to How to distribute complex perl based app by leocharre

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.