It comes with that option, but does the option work well?

If you write that as your Makefile.PL and then run it, you'll get error messages. Why? Because you don't have some of the files that passthrough says you require built yet.

If you're like me, you look at it and think that you need Module::Build::Compat to be loaded and run to crate them. So I did that. And got rid of all errors. Then built my tarball.

If you avoid errors by doing that under Linux, you'll actually wind up with an uninstallable tarball. Why? Because certain things have just been loaded by force, and are not overwriteable. What you need to do is have the passthrough, and ignore errors. When you build the tarball, the missing files will be built for you, but not until. (This was the case a few months ago. I don't know if it is now.)

I discovered this only after uploading to CPAN and having a CPAN tester complain about the uninstallable file. I didn't bother reporting the bug after I fixed it because the response the first time that I reported a bug dissuaded me from caring.

Perhaps this is better now. Perhaps not. As I mentioned, I didn't report it so I don't know. Besides, I explained to the CPAN tester what happened, I wasn't the first person that he saw make the mistake, and if that tester continued testing, then any other people making that mistake at least had a good explanation hand-delivered...

The fact that I didn't report it and I don't know whether it is fixed should be a red flag. Something is wrong with how they're dealing with the community. People in the community who're trying to communicate should not consistently become pissed off with the process. Once or twice, it is just some bad apples. If problems are consistent, at some point you really need to stop making excuses and say, "Why am I not being seen like I want to be seen?"

I submit that Module::Build has hit that point and should ask that question.

In reply to Re: Re: Re: Re: Re: Module::Build and the PPM by tilly
in thread Module::Build and the PPM by barbie

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.