-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Description
Hello, we have had a new NUT driver proposal at networkupstools/nut#1671 which included some combination of libmodbus-ascii sources as needed for that new driver to communicate with an UPS (I am double-checking with the author if that can work with released RTU support instead).
It seems that the libmodbus-ascii sources are around for a quite a while, so there may have been good reasons to not merge them into main codebase and distribute everywhere, e.g. not well enough tested, not too portable, known unreliable, or something around that?
Then there is also a legaleze question about mixing your LGPL with our GPL, if some sources are snatched from the libmodbus project to provide a (fallback at least) implementation for one of many optional programs that can be built in NUT...
Should we be wary about the codebase on technical grounds - that even authors deemed it not mature enough to release, and so insist on rewrite of the submitted NUT driver?
Alternately, maybe it just "fell through the cracks" and you can just merge and release it officially, so NUT with the new driver may just depend on the OS/distro provided builds of libmodbus package (like it already does with some other drivers added in the past year or two)? :)