Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

lockfile #141

Closed
jdx opened this issue Feb 17, 2023 · 0 comments
Closed

lockfile #141

jdx opened this issue Feb 17, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@jdx
Copy link
Owner

jdx commented Feb 17, 2023

Here's what we can do with a lockfile:

  1. we can make rtx local --fuzzy the default behavior (since the real version will be locked) which is probably what people expect
  2. we can set the plugin repositories so other developers doing need to manually install plugins that either aren't in the shortname repo or are supposed to use a custom location
  3. we could have an rtx upgrade command to update the lockfile to the latest matching version

People have asked about having a custom shortname repo, but I think number 2 here actually makes that unnecessary.

This was mentioned in this thread, although I am not sure that locking to a specific plugin commit sha makes sense:

@jdx jdx added the enhancement New feature or request label Feb 17, 2023
@jdx jdx added this to the v2 milestone Feb 17, 2023
@jdx jdx changed the title add a lockfile lockfile Feb 19, 2023
@jdx jdx removed this from the v2 milestone Mar 2, 2023
Repository owner locked and limited conversation to collaborators Mar 27, 2023
@jdx jdx converted this issue into discussion #414 Mar 27, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant