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.

Sign up for GitHub

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

Jump to bottom

Make Quiet mode the default? #51

Open
rgl opened this issue Sep 15, 2020 · 5 comments
Open

Make Quiet mode the default? #51

rgl opened this issue Sep 15, 2020 · 5 comments

Comments

@rgl
Copy link

rgl commented Sep 15, 2020

Can the default installation mode be changed from Passive to Quiet? Having an UI by default seems counter-intuitive to the intent of chocolatey having a purely CLI experience.
@jberezanski
Copy link
Collaborator

Sounds reasonable. @riezebosch what do you think?

@jberezanski
Copy link
Collaborator

Should there be a package parameter for Passive? Or not worth the effort?

jberezanski added a commit that referenced this issue Nov 3, 2020
@jberezanski
Use quiet mode by default in new runtime packages
cae1c71 
Existing packages will gain this once they are reworked to use the new
tools.

Implements: #51
jberezanski added a commit that referenced this issue Nov 3, 2020
@jberezanski
Use quiet mode by default in new runtime packages
be2fb74 
Existing packages will gain this once they are reworked to use the new
tools.

Implements: #51
@jberezanski
Copy link
Collaborator

Implemented in the "new" family of packages discussed in #45. The existing "versionless" dotnetcore-* packages will gain this too (probably soon).

@koolhand
Copy link

Hi maintainers, thanks for these packages,

I don't have a serious need, I'm just letting you know the behaviour I'm seeing: when I choco update, I only get one interactive installer and that's dotnetcore-desktopruntime. So this is just a "me too" for suggesting silent a silent installation should be the default.

I think silent is the expected default for all choco packages. I found this buried in the chocolatey docs for Install-ChocolateyInstallPackage > -SilentArgs

Please include the notSilent tag in your Chocolatey package if you are not setting up a silent/unattended package. Please note that if you are submitting to the community repository, it is nearly a requirement for the package to be completely unattended.

Thanks again for maintaining, I appreciate it.

@jberezanski
Copy link
Collaborator

The existing "versionless" dotnetcore-* packages will gain this too (probably soon).

I've finally made the effort of converting the versionless packages to reference the modern, version-specific ones, which do set /quiet by default. (so it turned out "soon" meant: "in a year or so" 😉 )

The docs about -SilentArgs unfortunately conflate two distinct aspects: visible/invisible installation progress and automatic (unattended) installation versus requiring user input. Of the two of them, the second aspect is much more important - yes, packages on chocolatey.org should be unattended (i.e. not require user input). The other aspect was historically not very regulated and often was the result of personal preferences of a given maintainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rgl @jberezanski @koolhand