Why no update to portmidi version 217?

Asked by Sebastian Stark

I want to kindly ask if there is a specific reason why this library is not updated to version 217, which is available for quite some while. There are third-party bindings that fail to build against this older version and it is not trivial to build the new version of libportmidi on Ubuntu.

From looking at the portmidi svn repository the changes between 200 and 217 seems to be minor. It mainly seems they decided to build some java application by default, which could be patched out.

I would also offer my help for testing, if that is useful at all.

Sebastian

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu portmidi Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

I suggest you report a bug. If the bug and security fixes are significant then the package will be updated sooner rather than later. If the gains are only slight then the package will be left.

There may be a PPA for it here on Launchpad.net

Revision history for this message
Sebastian Stark (sebstark) said :
#2

I don't know if it's a bug. Also, I mistakenly assumed the problem would go away by updating the package to the most current version. I backported portmidi217 myself now and still the problem persists. I will try to describe it:

libportmidi from that package is linked to libporttime. However, if I compile libportmidi myself, without using dpkg-buildpackage but the supplied cmake system, I get a version of the library that is not linked to libporttime. When I try to link some go bindings to portmidi I get an error unless I remove libporttime from the linker flags.

This only happens when I link against the ubuntu packaged version of libportmidi, it does not happen for my own build or on e. g. macos using the same code. See also this discussion on github:

  https://github.com/rakyll/portmidi/issues/27#issuecomment-241283155

As I said, I do not know if that counts as a bug, but it is something stopping Ubuntu and Debian users to use libportmidi for some projects.

Can you help with this problem?

Provide an answer of your own, or ask Sebastian Stark for more information if necessary.

To post a message you must log in.