Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I checked the Module::Build's bug queue today and unsurprisingly found that 0 new bugs/requests had been added and 0 new comments had been added to existing tickets. There's no new traffic on nor on

There is, however, lots of additional commentary here. I'm not even going to get into the validity of any of it, I'm just going to say this: A POST ON PERLMONKS IS NOT A BUG REPORT. It is not a feature request. It is not a wishlist or todo item. It does not get back to the author. I maintain MakeMaker. I do not normally read Perlmonks. Ken Williams maintains Module::Build. He's not a regular reader of Perlmonks either. Even if we were it puts extra load upon the author to have to mine Perlmonks for nuggets of bugs and feature requests.

IF THE INFORMATION DOES NOT GET BACK TO THE AUTHOR IT IS USELESS. By talking about your likes and dislikes of modules on Perlmonks you are participating in a giant reporting circle jerk. You do not aid or alter the development of the software you use and comment on. It has 0 effect.

I don't really give a crap about people bashing MakeMaker or Module::Build. I do give a crap when folks complain that we're unresponsive or secretive and then I look and see no traffic on the list or in the bug report queue.

REPORT YOUR PROBLEMS TO RT AND THE LIST. If no one answered, report it again. If someone already reported it and nothing's been done about it, throw in a "me, too" so the authors can get an idea of how many people the problem effects. Ken and I are very busy. We maintain some of the most critical CPAN modules. Sometimes it can take use months to fix a bug or add a patch. But if its in the RT queue it means it will not get dropped on a floor and lost.

In reply to AUTHORS DO NOT SEE ANY OF THIS by Anonymous Monk
in thread Module::Build users -- please use the "traditional" create_makefile_pl option by perrin

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and a log crumbles through the grate...

    How do I use this? | Other CB clients
    Other Users?
    Others making s'mores by the fire in the courtyard of the Monastery: (5)
    As of 2018-02-18 04:52 GMT
    Find Nodes?
      Voting Booth?
      When it is dark outside I am happiest to see ...

      Results (250 votes). Check out past polls.