On 2015/07/01 14:18, Raf Czlonka wrote: > Sure, I could update the port to a newer version but if there's a bug in > the actual *software*, I'm afraid that I won't be able to do much as I > don't know C - maintaining a port for a software written in language one > does not understand is probably not the best of ideas.
That's not a requirement for being a maintainer, btw. Things like testing new versions and communicating with upstream if you run into problems are often enough. Though of course it's not necessary to take on maintainership to send a diff. I echo jca's advice, it would be nice if upstream decided that it's at a suitable point to be worth generating a release tar.gz. I don't see any requests for that on the mailing list, it wouldn't hurt to ask (maybe they don't want to go the trouble; OTOH maybe they will be pleased that somebody is taking an interest). Sometimes it's worth going to the trouble of making and hosting your own distfile from a VCS checkout, but in that case it's really a good idea if the port has an active maintainer who is willing to track upstream's commits and pick up on important changes.
