devel/paq-nvim: New Port, minimal Neovim package manager

[agh_riseup.net]

Summary

Paq is a minimal, simple to use packer manager for Neovim written in Lua. Paq
is aimed for Neovim users who make use of Lua for their configuration language.
Paq is written to make use of existing Neovim features, and to have a simple
and familiar interface for declaring packages.

https://github.com/savq/paq-nvim

[agh_riseup.net]

Improve notes in pkg-message.in

[diizzy]

Can you elaborate a bit on why this is needed as it seemingly will interfere with our own package framework? It's not possible to package plugins directly?

[agh_riseup.net]

In D42185#965792, @diizzy wrote:

Can you elaborate a bit on why this is needed as it seemingly will interfere with our own package framework?

OK, I am not at all clear on how this interferes with pkg, as the plugin, thru Neovim will only write config or state to the user's home directory.
The aim here is make it easier for FreeBSD users to install a Neovim package manager, and take comfort in the fact that it is managed thru the Ports framework, also, a package manager is normally the start of customising one's Neovim environment. What should be considered a fundamental component of an editor these days, the package manager is not yet part of the editor, such is the state of modern tooling. Moving the plugins into the Ports removes some of the nightmare of managing plugins from the User to the Port maintainer.

It's not possible to package plugins directly?

Farken oath it is, and guess what, there is more Neovim plugin Ports coming from me :-D

[agh_riseup.net]

• Update to 2.0.0
• Cleanup files/pkg-message.in

[diizzy]

That made things a lot clearer, I was a bit concerned that it would "pollute" /usr being described as a package manager. While there are no restrictions on packaged applications in terms of operation (excluding harmful software etc) it's good if we can keep installed files from packages unaltered and not trying to "work around" the ports framework whenever possible.

[agh_riseup.net]

In D42185#968867, @diizzy wrote:

That made things a lot clearer, I was a bit concerned that it would "pollute" /usr being described as a package manager. While there are no restrictions on packaged applications in terms of operation (excluding harmful software etc) it's good if we can keep installed files from packages unaltered and not trying to "work around" the ports framework whenever possible.

I think I am understanding you concerns. paq-nvim is a successor to packer.nvim (https://github.com/wbthomason/packer.nvim), a Port of which I was sitting on for over a year, big mistake. During that time, using nvim with packer as a user, and sometimes as root, I noticed no clobbering of the pkg managed file name space below /usr/local, or more specifically, /usr/local/share/nvim, a concern I also had from the start, and have attempted to monitor and manage. A plus to note, Neovim makes use XDG environment configuration too, which makes organising and house keeping of one's configuration much easier; this method I prioritise for my Neovim deployments. After packer development stopped, and paq started, I have had less time to test, however, I have noticed no clobbering of /usr/local/share/nvim/.

One can run :lua print(vim.o.runtimepath) from within neovim to print the runtime configuration paths too.

[diizzy]

Committed with some minor changes to text, thanks for your contribution!