So, how does the module fail if there is no COM1 available? What does the module do that prevents it from installing without tests when there is no COM1?

If you are willing to put in the work to make the fixes you need, maybe you can talk to the author whether they give you co-maintainership so you can release a fixed version.

As a note, the format for the bug email address is bugs-$module_name@rt.cpan.org, so in this case, bugs-Win32-SerialPort@rt.cpan.org. You can also just log in with your PAUSE credentials instead of Bitcard or OpenID (which is Google, Facebook and some others I think).

Update: It seems that Makefile.PL insists on finding COM1 and bails out if it is not available. So a very simple approach would be either to install the module without running Makefile.PL or to delete the lines writing to COM1.

I see no patch on RT for that issue. A working and tested patch is often easier for a maintainer to apply than griping about the issue.

On the other side, the maintainer already has stated that they don't see the issue as a problem, so maybe enabling the module to be installed without running Makefile.PL is a better approach.

In reply to Re: Serious issues with Win32::SerialPort by Corion
in thread Serious issues with Win32::SerialPort by rdiez

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.