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

Command choco list should list local packages when called with no parameters #1701

Closed
vexx32 opened this issue Jan 3, 2019 · 2 comments
Closed

Comments

@vexx32
Copy link
Member

vexx32 commented Jan 3, 2019

Disclaimer: I am a casual user who frequently forgets I have chocolatey installed.

As such a casual user, when I remember I have Chocolatey installed, I enjoy being able to update the packages I have installed without manually going and figuring out where they came from myself.

However, it seems strangely obtuse to figure out how to just list the packages I have installed. Most package managers I've dabbled in tend to assume that when I look for a list of packages, I generally want to look at already-installed packages first.

Chocolatey does not. If you call choco list with no other parameters, it assumes you want every single possible package that is available. I have never wanted this, not even once. Were I to want it, I would expect that a call such as choco list * would have this behaviour.

Instead, I have to muddle through the help screens until I stumble across --local-only. So it's about twice as many keystrokes just to get at a list of things I have installed. What is the motivation for this?

I genuinely am having difficulty understanding why it's preferable behaviour to bog down the package servers with a "give me all packages" request as the default behaviour of calling choco list. If there is a reason, please enlighten me. 😄

@ferventcoder
Copy link
Member

Duplicate of #158

@ferventcoder ferventcoder marked this as a duplicate of #158 Jan 3, 2019
@ferventcoder
Copy link
Member

FWIW I completely agree with your thoughts. This behavior was inherited by the way that NuGet works. Please see #158 for where this is going to be added as it is a breaking change.

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

No branches or pull requests

2 participants