Serious issues with Win32::SerialPort

rdiez has asked for the wisdom of the Perl Monks concerning the following question:

Hi all:

Win32::SerialPort has not seen a release since 2010. This bug is becoming a serious issue for me, I just cannot distribute my Perl script smoothly:

https://rt.cpan.org/Public/Bug/Display.html?id=89837

This other bug is just not getting attention:

https://rt.cpan.org/Public/Bug/Display.html?id=120068

The CPAN bug tracker is weird. I haven't figured out yet how to get the e-mail address for a bug, in order to contribute to it. The bug tracker does not state clearly how to create a new account for the web interface, it wants you to use a "Bitcard account" or some OpenID. It has been user-unfriendly for years. A bit like perlmonks.org , where the "Title" box above is just too short. This all smells of rot.

What's the best way forward, at least for Win32::SerialPort? Is there an alternative? Or is the only way forwards to fork it?

Thanks in advance,
rdiez

Comment on Serious issues with Win32::SerialPort

Replies are listed 'Best First'.
Re: Serious issues with Win32::SerialPort by Corion (Patriarch) on Aug 03, 2017 at 07:59 UTC
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.	[reply] [d/l] [select]
Re: Serious issues with Win32::SerialPort by marto (Cardinal) on Aug 03, 2017 at 08:25 UTC
"What's the best way forward" If I were depending on this I'd write a patch and raise a ticket, linking any other issues the patch addresses. "I haven't figured out yet how to get the e-mail address for a bug" It's cunningly hidden behind a link which reads 'report a new bug', which provides a link along with instructions on providing patches/bug details. "A bit like perlmonks.org , where the "Title" box above is just too short." It scrolls when you type.	[reply]
Re: Serious issues with Win32::SerialPort by Anonymous Monk on Aug 03, 2017 at 09:31 UTC
Win32::SerialPort has not seen a release since 2010. This bug is becoming a serious issue for me, I just cannot distribute my Perl script smoothly: Change the way you distribute your script (distribute your fork of this module)? Also fork it now and upload the fork on the internet (cpan/whatever), direct your users to use your fork, report your fork to the maintainer (its a patch) and move on with your life Also see old wisdom Re: Device::Modem Find which Port Modem is connected to	[reply]


Problems? Is your data what you think it is?
	PerlMonks