camspiers / luarocks Goto Github PK

I think it has something to do with dbus_proxy entrypoint structure(it's a directory) but I don't think the rock is broken, maybe it relies on some deprecated import behaviour. I can't say for sure because I am not a lua developer.

moving init.lua out of dbus_proxy directory at ~/.local/share/nvim/lazy/luarocks/.rocks/share/lua/5.1 and renaming it to dbus_proxy.lua made it available

Under some circumstances and on certain setups require("luarocks") will return the real Luarocks API.

To prevent awkward clashes it might make sense to rename the whole namespace to nvim-luarocks or something of the like :)

dbus_proxy luarock specified in the config like this:

{
  "camspiers/luarocks",
  dependencies = {
    "rcarriga/nvim-notify",
  },
  opts = {
    rocks = { "dbus_proxy" },
  },
},

doesn't get installed automatically after build or on launch unlike "fzy" from the example.
My workaround is to just use :RocksInstall dbus_proxy but it introduces a manual step in the process of setting up my neovim config.

Hey,

Given that Neovim already bundles its own Lua interpreter, is there any incentive to keep the LuaJIT installation process in the build.lua? It seems to not affect behaviour in any meaningful way when I tried modifying the plugin and running without that specific step. It could cause luarocks to use some other lua version internally, but to my knowledge that does not change anything.

It's definitely the build step that takes the longest so eliminating it would be nice :)
If we're okay with the change I can make a pull request for it (or you could perform the change if you prefer).

Thanks!

Needs to create .rocks folder for rockspec in ../lazy/luarocks/ or whatever path is used
otherwise, writing the rockspec file fails