Uh, you keep saying stuff like this, but your only support for it appears to be that you made a suggestion on the list that wasn't accepted.

No. I just happen to be one of many who think the same way. And we've all been disregarded. How many folks have you seen in this thread or the other M::B threads saying the same thing? How many people have said the same thing elsewhere? When that many people hold the same opinion, even if I dont agree with it I'll respect it. It seems that the M::B crew think otherwise. And IMO those who think this breakage is acceptable or even a good thing are in the minority.

Regarding your Win32 comments, they dont wash. I _have_ nmake on my PC (and its freely downloadable in at least two forms) I also _have_ a C/C++ compiler on my PC (and a free version of cl.exe has been available from MS for some time now.) So im one of those folks who can get just about any module that doesnt have Linux specific library issues to install. EU::MM runs out of the box on my box, why shouldnt M::B? And if somebody files bug reports on a system that you dont directly work with dont you think it should be followed up on? I know I do.

Ultimately I hope M::B works out. But I think part of that will involve backing off from some of the decisions made, and possibly doing some community outreach. As it is M::B has a bad rep basically for a small set of reasons and until someone decides remove those causes I suspect itll stay that way.

Oh, and as a last thought has it occured to you what might happen? Folks might get so sick of M::B incompatibilities that they start parallel maintaining normal distros. How would you feel if someone started redistributing your work under a new name just becuase you decided to use M::B? To be honest I can see it happening. And that would just make the current EU::MM situation worse wouldnt it?


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi

In reply to Re: Re: Re: Re: Re: Re: Re: Module::Build and the PPM by demerphq
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.