paq-nvim VS luarocks

If you want a dead simple package mamage that only puts packages in opt and start, you can use paq.nvim

Is there anyone here who can share some feedback on how much lazy.nvim has been better than what you were using previously? If my context helps, I'm using paq-nvim, previously was using packer.

This was a problem when I was using paq as my manager, now I have the same problem with packer. It never happened when I wanted to install new plugins, only on updating. With packer I have a workaround: after it fails to sync it allows to re-run all failed jobs, and each times about a half of failed jobs fail again, others update successfully, so I can iteratively sync everything, but that's a terrible waste of time;

Options: - packloadall command family and maybe git submodules - minpac which is a thin utility around the above - vim-plug - old but still popular for it does the job - packer.nvim is a popular choice for lua configs, never got to using it myself - paq-nvim is another often mentioned lua solution - dozens of other solutions

that sounds like paq, but slow?

On my Neovim setup, I simply have the following plugins. I use paq as a plugin manager:

paq.nvim

LUA_INCDIR is not listed on either https://github.com/luarocks/luarocks/wiki/Installation-instructions-for-Unix or https://github.com/luarocks/luarocks/wiki/Installation-instructions-for-Unix but luarocks complains that it's not set. What does it do?

Luarocks packages (or "rocks") provide a rockspec, which luarocks uses to build the package and resolve dependencies.

The luarocks.loader module is provided by Luarocks and basically replace the standard require function by a version that handles Rocks installed with Luarocks (https://github.com/luarocks/luarocks/wiki/Using-LuaRocks#multiple-versions-using-the-luarocks-package-loader and https://github.com/luarocks/luarocks/blob/master/src/luarocks/loader.lua). Note that this is safer than your implementation since it "knows" the running Lua version and the corresponding Luarocks installed files. So it will automatically load modules at the correct version / path (without additional set_path and hard coded string).

I would reccomend you use luarocks for the project. It’s the “standard” package manager for lua, and supports building the C parts (using autotools). It also manages the dependencies for you!

What kinds of trouble? It looks like it's under active development https://github.com/luarocks/luarocks/commits/master ...have your troubles with it been specific enough things that you could post them in the issue queue?

what luarocks version are you running? If it is the one from luaForWindows, then I recommend upgrading it (https://github.com/luarocks/luarocks/wiki/Download). Solved my include problems but requires a bit of configration