Lucas <lu...@sexy.is> wrote:
> It's currently running on my -current instance without any issue
Of course, as soon as I sent this email I remembered I forgot to check
if the new plugin manager with LuaRocks works. It does, but not out of
the box: it's invoked as `luarocks`, while it should be `luarocks-5.3`
in this case. I could patch it to literal `luarocks-5.3`, but I think
it would be more correct to patch it to something that doesn't force me
to keep both in sync, something like `luarocks-${MODLUA_VERSION}` and
then replace. Is that the correct approach? Patching like that and then
adding a `post-patch:` target using ${SUBST_CMD}?
