Thank you.

I just realized what I don't like about approach (1), which is superior in every other aspect.

For modules' author there's virtually no difference between the three approaches. One way or another, it's going to get scripted.

However, as a side contributor, I would prefer to know there's more than just one module. Is my bug specific to just one plugin? Am I changing some boilerplate and/or generated code? Is this change compatible with the author's tooling? And the answer to all of these is just ls.

That said, I'm not sure whether it's just me, or there are others who feel that way.

In reply to Re^2: Multiple CPAN distributions under the same git repository? by Dallaylaen
in thread Multiple CPAN distributions under the same git repository? by Dallaylaen

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.