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.

Sign up for GitHub

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

Jump to bottom

[Discussion/update] how to handle dev packages #371

Open

mrcjkb opened this issue Jan 31, 2025 · 0 comments

Labels

discussion enhancement

Member

mrcjkb commented Jan 31, 2025

with the ability to install dev packages, we currently never regard them as outdated, because there's no way to compare the version.

Some ideas:

For dev manifests, we could perhaps check the source hash and compare it with the one in our lockfile, to determine if it's changed. This would require a download of the source.
Another option, which is what rocks.nvim does, is to always treat dev packages as outdated so they always get reinstalled.

I kind of prefer the first option. It would require us to implement a new manifest type.

mrcjkb added discussion enhancement labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment