lazy.nvim/lua/lazy/core
Roger Kim 80da254e64
fix(rocks): add lib64 plugin directory to package.cpath (#1717)
## Description
`package.cpath` is missing the `lib64` directory for plugins that have
luarocks dependencies.

## Context
I found this issue when I was working on my new Neovim plugin on my
Fedora 39 machine. I added the `luasockets` dependency to rockspec file
in my plugin like so:

```
rockspec_format = "3.0"
package = "typeracer.nvim"
version = "scm-1"
source = {
	url = "git+https://github.com/carbon-steel/typeracer.nvim",
}
dependencies = {
	"luasocket",
}
test_dependencies = {
	"nlua",
}
build = {
	type = "builtin",
	copy_directories = {},
}

```

I found that the dynamic libraries from the `luasockets` dependency were
installed like so:
`/home/username/.local/share/nvim/lazy-rocks/typeracer.nvim/lib64/lua/5.1/socket/core.so`.
However, the only entry related to my plugin `typeracer.nvim` was:
`/home/glyph/.local/share/nvim/lazy-rocks/typeracer.nvim/lib/lua/5.1/?.so`.
The issue is that we only have the plugin's `lib` directory in
`package.cpath` and not `lib64`.

I looked through `lazy.nvim`'s code and I think adding the `lib64`
directory should fix the issue. I don't know if we also want to worry
about `lib32` as well, but so far, this change works for me.
2024-08-31 08:58:43 +02:00
..
handler feat: add plugin name to handlers.managed 2024-07-11 22:04:06 +02:00
cache.lua style: fix some typo (#1496) 2024-06-03 09:18:43 +02:00
config.lua docs: update dev.path description (#1711) 2024-08-31 08:57:58 +02:00
fragments.lua fix(fragments): check for empty plugin names 2024-06-25 00:31:34 +02:00
loader.lua fix(rocks): add lib64 plugin directory to package.cpath (#1717) 2024-08-31 08:58:43 +02:00
meta.lua fix(meta): resolve deps from meta instead of fragments. Fixes #1566 2024-06-27 10:21:54 +02:00
plugin.lua fix(plugin): make .lazy.lua work again 2024-07-24 07:23:36 +02:00
util.lua fix(util): strip `-lua` in normname 2024-07-11 22:03:53 +02:00