I am developing a music player and want to list all types that my music player's Game_Music_Emu plug-in can play. I can iterate through types with gme_type_list(), but all I can retrieve about each gme_type_t through the C API are the name of the console it's associated with (gme_type_system()) and whether the type supports multiple movements (gme_type_multitrack()). I'd like to be able to look up the most common extension associated with a track. I can go from extension to type (gme_identify_extension()), but not the other way around.When a library has become widely forked, what's the best way to get a simple feature request into all of them, especially the version that makes it into popular free operating system distributions' package repositories?
Getting a feature into multiple Game_Music_Emu forks
Moderator: Moderators
Getting a feature into multiple Game_Music_Emu forks
So I found a conspicuous-by-absence missing feature in the API of Game_Music_Emu, a library that blargg appears to no longer maintain (but correct me if I'm wrong). I've reported it to maintainers of various distributions of GME: kode54, mpyne, and the Ubuntu team. Here's what each report looks like:
Re: Getting a feature into multiple Game_Music_Emu forks
Pick the leading fork.
Re: Getting a feature into multiple Game_Music_Emu forks
Then the problem becomes convincing distributions to follow the leading fork.
Re: Getting a feature into multiple Game_Music_Emu forks
Circular definition, the leading fork is the one distros follow.
- rainwarrior
- Posts: 8732
- Joined: Sun Jan 22, 2012 12:03 pm
- Location: Canada
- Contact:
Re: Getting a feature into multiple Game_Music_Emu forks
Create a new fork and declare all the others to be heretics.
Re: Getting a feature into multiple Game_Music_Emu forks
The fork in the leading number of distributions is not necessarily the fork that leads in feature development.calima wrote:Circular definition, the leading fork is the one distros follow.