packer.nvim icon indicating copy to clipboard operation
packer.nvim copied to clipboard

Allow for system package luarocks

Open wbthomason opened this issue 4 years ago • 4 comments
trafficstars

Add an option to allow the luarocks functionality to use a system-level luarocks package, if installed, rather than re-installing luarocks and luaJIT via hererocks.

wbthomason avatar Jan 25 '21 15:01 wbthomason

This will break sandboxing, ie with firejail, as luarocks does not conform to XDGBDS.

matu3ba avatar Feb 12 '21 23:02 matu3ba

@matu3ba: could you say more? This would not allow the luarocks module to install to or uninstall from system-level rock trees, but just avoid installs if a rock already exists. Does that still break sandboxing in an undesirable way?

wbthomason avatar Feb 16 '21 00:02 wbthomason

@matu3ba: could you say more? This would not allow the luarocks module to install to or uninstall from system-level rock trees, but just avoid installs if a rock already exists. Does that still break sandboxing in an undesirable way?

Sorry for not explaining properly. The behavior occurs for firejail, which is the easiest to use (and fairly complete) sandboxing solution for Linux desktop programs (I tested luarocks).

What happens is that luarocks downloads the manifest to $HOME and errors out in a unexpected way (and very unclear way) about not finding proper paths, because default sandboxing only allows data access to often necessary paths of applications like .config, .local. Access to "unknown paths" in $HOME like .luarocks is forbidden on default, unless there is a profile for the application.

When do you plan to implement this?

matu3ba avatar Feb 16 '21 10:02 matu3ba

I certainly won't be implementing this before March, and I'd characterize it as not very high priority.

wbthomason avatar Feb 16 '21 14:02 wbthomason