-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add aliases for installation and uninstallation #2303
Comments
+1 |
This is something I would also upvote for, except making remove, etc.. an alias for uninstall. |
Not sure why you are against making remove and alias for uninstall. Even NPM has that...
|
If anyone has any strong opinions on aliases, i.e, if any others should be added, please post a comment on the linked PR |
Description of the new feature / enhancement
Make
add
andi
aliases forinstall
in winget.add
is used by NPM, by the yarn package manager, and by cargo-edit. Different names improve the experience for newcomers, which, if they come from different package managers, might be used to different names for installing packages, and it would be delightful if they just work.Also add
r
orrm
andremove
as aliases touninstall
.remove
is used by the apt-package manager, so it would be helpful if users of apt can have the same feel with Winget. One letter subcommand aliases might feel wrong, however, NPM has one for installation. Another option is to haveu
as an alias for uninstall, though I don't recommend it.Could also add
ls
as an alias forlist
. However, it depends on how much the team focuses on UX or DX. I personally strongly suggest those aliases, which need to be strongly tied to historical command names. For example, the apt package manager for linux was perhaps the oldest and most popular, and it has theremove
keyword for removing a package. So if we reuse its subcommand names, we reduce the friction.Notes
One downside is this would give us fewer names for new commands. However, I think that if the package manager makes two similar names for different commands, then it is not a good package manager, solely for that reason. My experience with the rustup package manager in particular strengthens that feeling about similar names, because it has both a target subcommand and a toolchain subcommand and I always mess them up.
Edit: I want to show you the NPM package manager
npm-install
synopsis:https://docs.npmjs.com/cli/v8/commands/npm-install
What do you think?
Proposed technical implementation details
Make
i
,add
aliases forinstall
, and document them, including in the help page. Makerm
andremove
aliases foruninstall
and document them in the help page as well. Makels
an alias forlist
.The text was updated successfully, but these errors were encountered: