I’m prepping a MacPorts update for omniORB and omniORBpy (to versions 4.3.2; Portfiles are ready to go) and noticed that omniEvents (version 2.6.2; a separate package) needs at least a bit of code polishing to be compatible with new compilers and new omniORB.
The last updates for omniEvents on SourceForge were 16 years ago. There is a fork on github for RedHawkSDR (software-defined-radio) which has afaict small adjustments as recently as two years ago. Not sure if that project is actively using omniEvents. Should I pursue patching omniEvents source code to build for MacPorts, or pursue working with the fork, or would it be preferable to retire it as a package? Let me know what y’all would suggest or prefer… - Tom
