#18870: solfege-3.14.0 Submitting portfile for new port --------------------------------------+------------------------------------- Reporter: allencmcbride@… | Owner: raimue@… Type: enhancement | Status: closed Priority: Normal | Milestone: Port Submissions Component: ports | Version: 1.7.0 Resolution: fixed | Keywords: solfege new port Port: solfege | --------------------------------------+------------------------------------- Comment(by allencmcbride@…): Rainer, you're right. One needs to point Solfege to an external MIDI player. I've been making a dumb mistake this whole time: I've had my ~/.solfegerc file hanging around from a long time ago, and it's been telling Solfege where to find my MIDI player, even on first run after a fresh installation. I had assumed it was finding and using Apple's built- in MIDI player, but I should have known better. Now Apple does not come with a command-line MIDI player, am I right? If I'm right about that, then I think I should just include qtplay as a runtime dependency in my portfile. And hopefully I'll find out soon how to tell Solfege during installation where to find qtplay. Otherwise, a user will have to be told to go into Solfege preferences and do two things: 1) Point to qtplay under "External Programs", and select "Use external MIDI player" under "Sound Setup". Obviously not the smoothest user experience. I'm sorry about all this; clearly I still have a lot to learn. If you think it best, feel free to un-commit this thing until I have this problem worked out. -- Ticket URL: <http://trac.macports.org/ticket/18870#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS