-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Feature] Allow downloading a specific plugin version #222
Comments
I vote for "version" as the argument name. But effectively we expose another problem: we don't track things like minimum (and maximum? is that ever a thing?) plugin versions in the dependency listings. Many huge scripts would benefit from that as well. |
Hmm yes dependencies... this should only be an issue for scripts or some complex plugins like https://github.com/AmusementClub/vs-mlrt Currently deps look like this:
We could add something like this:
But I'm not sure if python has a smart-enough build in version comparison function + someone needs to verify the min/max versions... Alternatively, we could allow only specific plugins to downgrad with "allow-downgrade" / "can-downgrade". |
You don't need it, the release list is in version order (more or less) so you'd only need to locate the strictly matching version with string comparison in the list of all releases. As a simple hack. Writing a version comparison function also isn't that hard... |
It would be nice if vsrepo could install older plugin versions.
Something like
vsrepo install myplugin --version "1.2.3"
vsrepo upgrade myplugin --version "1.2.3"
The text was updated successfully, but these errors were encountered: