Hi, > On 14. Mar 2017, at 19:26, Kurt Jaeger <li...@opsec.eu> wrote: > > Hi! > >> databases/luadbi has been scheduled for expiry at 2017-04-30 due >> to being unfetchable. However, there is a patch at PR 212884: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212884 >> >> The patch has maintainer approval. If some committer could pick >> this one up before the port expires, that would be awesome. > > Done.
Thanks a lot! > What would it take to test the postgres option ? I’ll do that right away. > Is there a reason lua53 is not supported in this port ? If no, > would it be possible to add those options ? I’m not sure, unfortunately luadbi seems to be only sporadically maintained. As far as I know, prosody is the only port that depends on it. Once the luadbi port broke due to the shutdown of Google Code, I filed a bug against Prosody (https://prosody.im/issues/issue/747). They directed me to a Github repository to which they had exported the Google Code project ( https://github.com/mwild1/luadbi ). I then tried to make them at least add the version tags from the Google Code repo (see my issue https://github.com/mwild1/luadbi/issues/36 ), but I did not hear anything from them yet. To make things worse, there seems to be a conflicting version on luarocks. So I think the maintainer of the luadbi port just copied the files over to his private site. Long story short, the prosody maintainers seem to put only minimal maintenance effort on luadbi at the moment. Prosody itself is still running on lua51, so this could be a reason why there is no „official“ support for lua53. I CCed the port maintainer, maybe he knows something more. > And if you ask why it took so long: very, very busy committers… No worries, I did not pay anyone, so no criticism. Thanks again for the commit. Regards Michael
signature.asc
Description: Message signed with OpenPGP
