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
pull requests but my lighter-weight attempt this time seems ok as
far as workload for me. But it is probably a mishmash of what I used to do and
what y’all want me to do so feel free to get me on the right track.
Thanks!
- Tom
> On Sep 21, 2021, at 10:33 AM, Thomas Lockhart wrote:
>
That did it. Thanks!
- Tom
> On Sep 21, 2021, at 10:38 AM, Jason Liu wrote:
>
> Did you try manually running the `portindex` command to have MacPorts re-scan
> your portfiles?
>
> --
> Jason Liu
>
>
> On Tue, Sep 21, 2021 at 1:33 PM Thomas Lockhart <mailt
I’m having trouble updating the omniORBpy port file to support the latest
version of omniORBpy and latest versions of python. It’s been a good while
since I’ve done this, but (with the latest macports installed) it only wants to
recognize the orginal 27 and 36 ports as available even though I’ve
