Skip to content

Conversation

teto
Copy link
Member

@teto teto commented Jul 13, 2024

when I tried to add a plugin on NURR, I worried it wouldn't work (because it generated or needed C libraries etc and it was not possible to see the generated rockspec: "Push and prey". I would like to be able to see the generated rockspec before merging and I find it hard to run the action locally.

I quickly hacked something to be able to generate the rockspec bypassing the github action:
jq '.plugins[] | select(.name == nvim-telescope/telescope-fzf-native.nvim)' ~/nurr/plugins.json | ~/luarocks-tag-release/bin/rockspec-generator-json.lua.

I imagined 2 new executables:

  • rockspec-generator-jsonto generate a rockspec for nurr.
  • rockspec-generator-cli that one could run from cli with an argparse interface, aka rockspec-generator-cli --name toto --version 0.1 --dependency=plenary.nvim --dependency=nui.nvim.

What is your opinion on that ? is it something worth pursuing ?

@teto
Copy link
Member Author

teto commented Jul 13, 2024

cc @mrcjkb

WIP

jq '.plugins[] | select(.name == nvim-telescope/telescope-fzf-native.nvim)' plugins.json > ~/luarocks-tag-release/test.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant