-
Notifications
You must be signed in to change notification settings - Fork 6
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
How to update the napari-plugin-manager within an existing napari installation #71
Comments
I think this would be great, one of the boons of the split out IMO |
honestly, it could just be in the list, so it would be listed at the top with console, so the user could see there is an update |
I like it. Maybe it's time to make it an actual napari plugin, or do we want to special case it? |
I don't have strong feelings here. making it a plugin would be very meta. |
I love seeing this close notification! 🚀 Just want to drop in and say — I have been very hands off with this repo because I am overwhelmed enough with the main one (and docs), but I really love and appreciate the progress you have all made here, and especially all the upstreaming to related tools. ❤️ Thank you! 🙏 |
So we have this uncoupled
napari-plugin-manager
. It technically allows us to update it without having to update napari itself. Should we provide an easy way toself-update
the manager? Otherwise users would have to fire up a CLI to update the napari environment and who knows what will happen there :PI'm thinking either a button somewhere, or a message when a new version is available, or something similar. Hopefully the update is trivial and doesn't involve too many changes in dependencies.
WDYT? This is not urgent but came to mind while thinking about the distribution model.
The text was updated successfully, but these errors were encountered: