I'd consider it in terms of release cycle. If all the modules have the same release cycle I'd be strongly inclined to use the same version number. If the release cycles for the individual modules are sensibly disjoint I'd be inclined to use different version numbers. However if the modules are related (by API definition perhaps) but may have disjoint release cycles I'd use a major.minor.point version number scheme where interface changes imply at least a matching minor version bump across the suite and point bumps for individual module releases.

True laziness is hard work

In reply to Re^7: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker by GrandFather
in thread Clean smoke-test install for Inline based modules using Inline::MakeMaker by davido

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.