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

Package upgrading routine is currently unintuitive #87

Closed
dreymonde opened this issue Jun 27, 2018 · 4 comments · May be fixed by #135
Closed

Package upgrading routine is currently unintuitive #87

dreymonde opened this issue Jun 27, 2018 · 4 comments · May be fixed by #135

Comments

@dreymonde
Copy link

Mint is just awesome, but I think that the package update part can be improved. In particular:

  1. There is no command (or I don’t know one) that can update all outdated packages (just mint update would be nice).
  2. When you type mint update, you need to provide full package name (for example, mint update jakeheis/Ice), but mint list shows the name without the author name (so just Ice in this example).

My proposal is also to rename mint update to more Homebrew-like mint upgrade, but that’s totally up to you. I can try to resolve first two mentioned issues and submit a PR if you’re okay with that. Just let me know!

@dreymonde
Copy link
Author

@yonaskolb any thoughts on this? 🙂

@yonaskolb
Copy link
Owner

Sounds good. Feel free to open some PR’s.

In terms of the name, neither update or upgrade really communicates what it does. To do a normal update you can just run install without a version and if there’s a newer version it will install that. The current update is just sort of a re-install. I was even thinking of removing it and have a —force or —reinstall flag to force a new build.
Maybe it could then be repurposed into an update all as you suggest

@yonaskolb
Copy link
Owner

update replaced with install --force in #96

@yonaskolb
Copy link
Owner

mint install now supports specifying just the package name in #100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants