Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a lockfile mechanism #107

Closed
Tracked by #149
savq opened this issue May 1, 2022 · 0 comments · Fixed by #157
Closed
Tracked by #149

Add a lockfile mechanism #107

savq opened this issue May 1, 2022 · 0 comments · Fixed by #157
Labels
enhancement New feature or request

Comments

@savq
Copy link
Owner

savq commented May 1, 2022

A lot of issues with Paq right now stem from the fact that it doesn't have any kind of persistent state. All information is either in the user's configuration or in the git repo itself. However,

  • Expecting the user to add more information in their config defeats the purpose of Paq. They could just use git submodules...
  • Querying git using stdio is tedious and error-prone.
    • Lua has very limited string/stream manipulation facilities
    • Using libgit2 bindings seems to be out of the question :(

The easiest way to solve this seems to be storing information in a file so that Paq has an easier time telling what has changed since it was last called.

The lockfile could be used for "reproducible" neovim configs.

@savq savq added the enhancement New feature or request label May 1, 2022
@savq savq mentioned this issue Aug 3, 2023
15 tasks
@savq savq mentioned this issue Oct 20, 2023
@savq savq closed this as completed in #157 Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant