Support rocks.nvim?

[mrcjkb]

There's a new plugin manager, rocks.nvim, which uses a rocks.toml as the source of truth for plugins.

Here's an example. It should be pretty easy to parse.
One difference to most plugin managers is that it uses name-based installation (without a repo owner, because plugins are installed from luarocks.org, unless using the rocks-git module).
I don't know how dotfyle would handle this?

[codicocodes]

This looks completely reasonable, I'll put it in the Todo.

Currently Dotfyle relies heavily on the heuristic username/plugin-name when matching. Currently not doing custom matching for lazy-lock either. Lazy lock also does not include the username, so would need to be solved for both.

[mrcjkb]

Awesome 😄

Here's some info that could potentially help map plugins on luarocks from plugin-name to username/plugin-name.

• luarocks plugins usually have a "neovim" label, so you can find them at https://luarocks.org/labels/neovim
  (though I don't think there's a query parameter for machine readable output 😞 )
• Rocks have a "homepage" attribute, which for Neovim plugins will typically point to the repo.

We're currently working on rocks - a rewrite of luarocks (not fully functional yet, and the name isn't final),
which will hopefully provide an embeddable rust library when it's done. Maybe that could be more useful?