I've never been particularly keen on a lot of directories in the lib/ directory of my distributions. I know things like h2xs and other module tools want you to think that's a good idea, but I've found it much easier to just put everything in a flat directory.

lib/Module.pm lib/Helper.pm

I can easily grep the sources and do other multi-file sorts of things, but more importantly for me, I get to see all of the files in one place. Other people have their preferences. If you do everything right, no one is ever going to know: they'll install the module and get rid of the distribution and be none the wiser. :)

I can install them wherever I like by telling MakeMaker where to put them. My Test::Data breaks out the functions into separate modules, although you get to them through Data.pm. You can use whatever you like for the keys and values of the PM argument to WriteMakefile().

WriteMakefile( #... 'PM' => { 'lib/Data.pm' => '$(INST_LIBDIR)/Data.pm', 'lib/Scalar.pm' => '$(INST_LIBDIR)/Data/Scalar.pm', 'lib/Array.pm' => '$(INST_LIBDIR)/Data/Array.pm', 'lib/Hash.pm' => '$(INST_LIBDIR)/Data/Hash.pm', 'lib/Function.pm' => '$(INST_LIBDIR)/Data/Function.pm', }, #... );

Beyond that, it doesn't really matter.

--
brian d foy <bdfoy@cpan.org>

In reply to Re: Separate files for CPAN dist by brian_d_foy
in thread Separate files for CPAN dist by jacques

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.