Personally, I would separate 'A' and 'B' projects into two separate distributions, and then lay them out like this:

  MyDist::A root directory/

     Makefile.PL
     README
     CHANGES
     MANIFEST
     MANIFEST.SKIP
   
     lib/
        MyDist/
          A.pm
          A/
             A1.pm
             A2.pm
 
     t/
        test1.t
        test2.t
        ...

[download]

In A.pm, you'd use MyDist::A::A1; and use MyDist::A::A2; to pull in the helpers. If you do want just a top-level namespace, just remove all references to MyDist.

That's consistent with how most CPAN structures are laid out, so I'd stick with what works.

In reply to Re: perl Module and directory structure by stevieb
in thread perl Module and directory structure by pwagyi

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.