Mooneer Salem <[email protected]> writes: > sioclient is used for FreeDV Reporter support. Unfortunately the latest > from their main/master is needed because the release version is using a > different version of the socket.io protocol. If you have any suggestions > that would make it easier for you and others to package, I'd definitely > appreciate them.
As someone who packages ham stuff, but hasn't dealt with freedv as much as I'd like (on my round tuit list), and without being clear on things, my $0.02: all programs A should only depend on released versions of other programs B, should accomodate the most recent release, and ideally any release of B which was current in the two year's preceeding A's release. Any program that does not have a release every 6 months is unhealthy, more or less. Any program for which advice to run git master instead of the release, for people who are using rather than contributing, is unhealthy. As a packager, I file 'release is overdue' bugs sometimes. This is partly because packaging doctrine is to package releases. github culture is leading to "why do we need release; just grab git master", and this misses the point that releases are a named stable point that has been validated to be ok. I have also filed "stop using X" issues, when X is unhealthy for various reasons. So I think the questions are: Is there an open bug at sioclient that "release is overdue and project is unhealthy", more or less? If not, I think that's in order, just so everybody can be straightforward. Is it really necessary to use sioclient? You mention "FreeDV Reporter", but why couldn't both that and freedv switch to something else? There is grpc, mqtt, websockets, and surely other things. Is the release version of sioclient actually problematic, if the FreeDV Reporter site ran it too? Why is that site using a non-release version? 73 de n1dam _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
