What does install do to CPATH?

[resistorsoftware]

I print out my CPATH to see where Neovim is looking for shared libraries to use, and noticed blink has added some serious directory fluff to the cpath. Is this normal? Does this make sense? Is there a way to clean this up if it is not needed? Is there an explanation? Did I do something weird via *vim.pack.add()??

/usr/local/lib/lua/5.1/?.so;./?.so;/usr/local/lib/lua/5.1/?.so;/home/runner/work/neovim/neovim/.deps/usr/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so;/home/fizz/.local/share/nvim/site/pack/core/opt/blink.cmp/lua/blink/cmp/fuzzy/rust/../../../../../target/release/lib?.so;/home/fizz/.local/share/nvim/site/pack/core/opt
/blink.cmp/lua/blink/cmp/fuzzy/rust/../../../../../target/release/?.so 

[Saghen]

It's for loading the fuzzy module. I'd accept a PR normalizing the path if it bothers you too much

https://github.com/Saghen/blink.cmp/blob/main/lua%2Fblink%2Fcmp%2Ffuzzy%2Frust%2Finit.lua

[resistorsoftware]

If it is all normal and works fine, and we speak of nothing important in terms of correct functionality, then I am happy to ignore the looks of it. I am still trying to come to grips with the fact that every time a plugin or my init.lua runs, it can alter this cpath and add the same path 2 or more times! That is also an asthetic mess in a way.

[Saghen]

It's not the same path, one uses a lib prefix and one doesn't. See the comments in the link