Here's a couple of things I hacked together, they basically allow you to control timidity's patch set easily. Control is obvious; I did good online documentation.
Created attachment 39471 [details] timidity-update timidity-update for users and root. Hacks up ~/.timidity/current or /usr/share/timidity/current symlink to point to a patch set.
Created attachment 39472 [details] timidity.cfg timidity.cfg for the controller. This config file looks for the timidity.cfg for the current patch set in /usr/share/timidity/current, which is a symlink to /usr/share/timidity/patchset for the patch set, SO PUT IT THERE. It probably should look in ~/.timidity/current first or something.
This works with shompatches. Add more patch sets, like midia etc etc, using this as the control script. For EAW patches, move the /etc/timidity.cfg from eaw intto /usr/share/timidity/eawpatches/
do youu think you could post an updated timidity++ ebuild that will use these? That would be a big help.
Created attachment 39779 [details] timidity.cfg I decided to not be a prude and tested out the timidity.cfg I had in mind earlier. This one has the following logic: if (exists(~/.timidity/current)) use ~/timidity/current/timidity.cfg else use /usr/share/timidity/current/timidity.cfg In other words, it'll use the patch set the user selected; but if the user has not yet run timidity-update, it'll just use the system wide one set by timidity-update -g. It works.
Created attachment 39780 [details] timidity++-2.13.0-r2.ebuild You'll need to put the new timidity.cfg into ${FILESDIR}, as well as timidity-update. This ebuild will install them. I moved stuff around in the src_install() because I was having trouble with portage not installing the new config; what it was was that I had an /etc/._cfg0000_timidity.cfg from earlier and it wouldn't overwrite it. *shrug* I haven't repoman'd this, but I tested it, it works for me.
in portage. thanks.
