I own three modules on CPAN and plan to upload more. Here's the thing - I have very limited access to different OSes. In fact, I only have access to Solaris, Cygwin, and, occasionally, Redhat9. I depend on my userbase to tell me when something goes wrong and how to fix it.

I just spent 6 hours tracking down a warning in the latest mod_perl2 build ... a warning for something that neither I nor any employer of mine will never use. Why? It's my contribution. If mod_perl didn't exist, I would not have a job. In case you missed that, let me repeat it:

Without mod_perl, Apache, Perl, CPAN, and tons of other stuff, I would not have a job.

It's my payment for the hundreds of thousands of manhours that went into mod_perl. It's the way I give back for a product that is the preeminent product in its sphere.

Let me say this another way - you are the recipient of over 10,000,000 manhours of design, development, testing, retesting, refining, and tuning. For free. (There are almost that many manhours again devoted to the serious modules on CPAN. Just think about that.)

But, it's not completely free. The cost is your time and your expertise. You are using modules on platforms I simply cannot access. I need you and your OS. I need your testing time. I need your patches.

Don't give up. Take the time to at least submit the results of your tests. Just something like: make test > bugreport &2> bugreport; mail owner@isp.com < bugreport

Hit Enter and work in another window. That's all we ask.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

In reply to Re: Module compilation hell by dragonchild
in thread Module compilation hell by Anonymous Monk

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.