I would suggest that there is scope for both of your suggestions - I particularly like the SHA1 related suggestion since it helps assure the integrity of each installed module.

From a $Pkg::VERSION POV, IMO (& I speak as a CM practitioner of many years standing), there is no one standard approach since the degree to which version control is required will, in almost every case, be required to be flexible enough to handle situations varying from top-level module only, down to every module.

Furthermore, I'm interested in how your proposal would handle the situation whereby 2 otherwise separate modules are installed over the same directory space e.g. Some::Class::Frob & Some::Class::Nicate, each being a top-level module in it's own right, but neither is top-level when installed maybe an argument for version id on an individual basis.

A user level that continues to overstate my experience :-))

In reply to Re: <pkg>::VERSION, git, hashes, shipit, Class::MOP, Moose, perl core support - what NOW makes sense. by Bloodnok
in thread <pkg>::VERSION, git, hashes, shipit, Class::MOP, Moose, perl core support - what NOW makes sense. by otto

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.