To me, how you keep them in source control depends on how you envision them as distributions. If all of the modules are tightly coupled and you would never want to release one without another, then you would want to have 

MassSpec/lib/MassSpec/SVGIsotopeClusterGraph.pm
MassSpec/lib/MassSpec/ViewSpectrum.pm
MassSpec/lib/LipcutElementsIO.pm
MassSpec/lib/LipcutElementsIO/Search.pm
MassSpec/t/
MassSpec/Makefile.PL

[download]
etc.

If you had three separate components that could be maintained and updated separately, then you would treat them as three distributions: 

MassSpec-SVGIsotopeClusterGraph/lib/MassSpec/SVGIsotopeclusterGraph.pm
MassSpec-SVGIsotopeClusterGraph/t/
MassSpec-SVGIsotopeClusterGraph/Makefile.PL

MassSpec-ViewSpectrum/lib/MassSpec/ViewSpectrum.pm
MassSpec-ViewSpectrum/t/
MassSpec-ViewSpectrum/Makefile.PL

MassSpec-LipcutElements/MassSpec/LipcutElementsIO.pm
MassSpec-LipcutElements/MassSpec/LipcutElementsIO/Search.pm
MassSpec-LipcutElements/t/
MassSpec-LipcutElements/Makefile.PL

[download]
etc. etc.

And if all four of them are envisioned as separate components then you might have four dists, but I'm guessing it's not so, and I think I've played with <code> enough for now. ;)

In reply to Re: code-controlled module naming conventions? by hobbs
in thread code-controlled module naming conventions? by jae_63

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.