Ticket #18870 (closed submission: fixed)
solfege-3.14.0 Submitting portfile for new port
| Reported by: | allencmcbride@… | Owned by: | raimue@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | solfege new port | Cc: | |
| Port: | solfege |
Description
This is my first time submitting a port. Suggestions welcome. As I've discussed on macports-users, there are a few wrinkles when trying "port -t destroot", but it doesn't sound like they're serious.
Attachments
Change History
Changed 4 years ago by snc@…
- Attachment Portfile.2 added
tweaks. does this still function correctly for you?
Changed 4 years ago by allencmcbride@…
- Attachment Portfile.3 added
re-adding "education", this time as secondary category
comment:3 Changed 4 years ago by raimue@…
- Status changed from new to assigned
- Cc raimue@… removed
- Owner changed from macports-tickets@… to raimue@…
comment:4 follow-up: ↓ 5 Changed 4 years ago by raimue@…
- Status changed from assigned to closed
- Resolution set to fixed
At the start I get the message No module named _solfege_c_midi. I probably just need to configure an external player?
Committed in r48583.
comment:5 in reply to: ↑ 4 Changed 4 years ago by allencmcbride@…
Thanks very much for committing the portfile! I don't know what this error message means; I don't think I've seen it. But I will try to figure it out.
comment:6 Changed 4 years ago 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.
Portfile for new port of solfege-3.14.0