Of course, when a package is in need of an update and the maintainer is kinda slow on the rebound, be my guess ... update it. After all, these are for our community's benefit, and not for some sort of personal glory.
This is the bit that's causing me a bit of concern because I made a couple of observations here and then followed the instructions I was given and look what's happened
Let me try an explain this in the best way that I can.
You've packaged the tool and it works for you. That's a good thing.
You've posted a link so it can be tested. Neal said, he'll look at it later.
Neal has a pretty good idea of what other packagers (at least the ones that are helping at the moment) are doing ... and we are really quite busy.
You see, the package you updated is not a priority at the moment, which is why Neal will look at it later.
Other users learning to package may download your update and take a look (Open Source advantage over Proprietary) ... maybe some have some other enhancements to add ... maybe add a better GUI.
By the time our present lead dev gets to it at its state, it might change ... changelog. There can be several changes made by different people and everything should be added on the changelog unless of course one rather not add their names.
In the end it is really up to the maintainer to add a text file CREDITS or CHANGES ... sometimes we forget. ... why am I thinking of AS??
Now, Eddie, I'm sure you'll understand that it takes more than one acceptable package to join the ranks. But if you are persistent and keep coming up with good packages and updates, who knows?
I hope all this makes good sense to you because I surely do not want to repeat myself again.
Peace and much respect,