Just keep hammering on MB and keep fixing the bugs. And for god's sake, keep USING IT! If nobody uses ot the bugs won't get found and fixed
Which brings us back to my starting point - I'm not interested in developing a module-building module myself. M::B and EU::MM to me are two vehicles of delivering my product to my potential users. One of the two works, and the other doesn't. So common sense dicates that I use the working vehicle instead of the broken one.
I'm in the process of digging through EU::MM myself, because I want to create an integrated Crypt::SSLeay distribution that uses the information from the current Perl instead of relying on the handmade Makefiles derived from EU::MM output, so I understand your pain, but I also wonder why schwern hasn't turned the MM::* stuff into mixin-based modules, one mixin for the make flavour, and one mixin for the OS flavour.
I will /msg schwern the details and try to set up a wholly automated process that reduces the necessary manual steps to a minimum I hope.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
