New port: osc2midi

[agraef (Albert Graef)]

This is an OSC <-> Jack MIDI bridge, works with either Jack1 from MacPorts or Jack2 from Grame's JackOSX project (​http://jackosx.com/).

NOTE: This port should be installed from source (no binary package), so that it can be linked against JackOSX if it happens to be installed on the user's system.

[mf2k (Frank Schima)]

Cc'ing Ryan who is listed as a maintainer.

Some comments:

• Since it builds with cmake, this port should be modified to use the cmake portgroup.
• It mentions the currently non-existing osc2midi-devel port from #48161. Those ports should be merged into a single Portfile.

[agraef (Albert Graef)]

Replying to mf2k@…:

Some comments:

• Since it builds with cmake, this port should be modified to use the cmake portgroup.

This doesn't work, for reasons explained in ticket #48161.

• It mentions the currently non-existing osc2midi-devel port from #48161. Those ports should be merged into a single Portfile.

I didn't know that it was possible to build both stable releases and development snapshots from the same Portfile. I don't know how to do this, can you please point me to some relevant documentation? Thanks.

[ryandesign (Ryan Carsten Schmidt)]

It is possible to combine multiple installable ports into a single portfile, using the subport keyword. I don't think this feature has been documented yet, so you'll have to look at existing portfiles that use the feature.

It's useful when the two (or more) ports are similar in some way. I often use this when a single downloaded source file has multiple components that should be installable as separate ports. For example, the pure portfile​ has a pure-mode.el subport.

Some other MacPorts developers like to use this facility when multiple versions of a port should be offered (e.g. development and stable), and those versions are similar in how they build. The cmake portfile​ gives an example of this. I myself tend to keep these as separate portfiles. This is in part because I developed the ports before subport capability existed in MacPorts, but also because I sometimes run into the situation where the development version differs significantly enough from the stable version that using subports would be complicated. Also, the script​ I use for automatically updating the version and checksums of a portfile does not work when there are multiple versions of the software represented in a single portfile.

Also, see the graphviz​ and graphviz-devel​ portfiles. Note that the graphviz portfile has graphviz-gui and gvedit subports, and that the graphviz-devel portfile has graphviz-gui-devel and gvedit-devel subports. Merging all of these into a single portfile would be complicated. I tried this in the php portfile​, which currently has 224 subports (covering six versions of php having thirty-something modules each). It works, but is very complicated and I'm not sure I would do it that way again.

[agraef (Albert Graef)]

Ah yes, subports. I wasn't aware that these are used to combine stable and devel ports, too. I might give that a try next time. Thanks for clarifying.

Replying to ryandesign@…:

Some other MacPorts developers like to use this facility when multiple versions of a port should be offered (e.g. development and stable), and those versions are similar in how they build.

Yes, this is the case here.

I myself tend to keep these as separate portfiles.

Ok, now that I've already submitted them that way, can we just leave them as they are? The build process is utterly trivial, so I'd say there's not much to be gained from combining the two ports.

[kencu (Ken)]

In 687be318dc79ca2ac2dcf62c340c0be96a16aad5/macports-ports (master):

osc2midi: new port @ 0.2.3

OSC to JACK MIDI bridge
closes: #47823