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

Document options for Windows installer #1550

Open
2 of 3 tasks
teknowledgist opened this issue Sep 9, 2024 · 4 comments
Open
2 of 3 tasks

Document options for Windows installer #1550

teknowledgist opened this issue Sep 9, 2024 · 4 comments
Labels
enhancement New feature or request P3 (could) Annoying bugs that have workarounds, Interesting ideas

Comments

@teknowledgist
Copy link

Is your feature request related to a problem? Please describe.

A silent install (/S) on Windows installs within the user's profile. A manual install has the option to install for all users. There is no (obvious) way to do both.

Describe the solution you'd like.

I need to silently deploy Twine to a classroom, so I need a combined silent and all-user install option.

Describe alternatives you've considered.

I could probably write a PowerShell script to install for the current user (although the SYSTEM user is odd), move the files to somewhere write-protected for users, and adjust all the shortcuts, but that is messy. I'd rather not.

Additional context on this suggestion.

Maybe this already exists? If so, it needs a bit of documentation.

I wouldn't mind needing to download a different installer.

Presubmission checklist

  • I am interested in working on code that would implement this feature request. (This is not required to submit a suggestion.)
  • I have done a search and believe that an issue does not already exist for this idea in the GitHub repository.
  • I have read and agree to abide by this project's Code of Conduct.
@teknowledgist teknowledgist added the enhancement New feature or request label Sep 9, 2024
@teknowledgist
Copy link
Author

I want to add that a silent install for the current user and a manual install for all users seems functionally backwards.

Why does the current user need a silent install? If we equate key clicks to mouse clicks, it is more clicks to install silently than to install via mouse. If a user is advanced enough to use a silent install, why would they care if it is machine-wide since they can still use it?

Likewise, sysadmins who deploy software to machines for all users must have a silent install option.

Thus, if there is a silent install option at all, it should default to an all-users install, and an install for the current user requires doing it manually.

@klembot
Copy link
Owner

klembot commented Sep 10, 2024

@teknowledgist Twine uses NSIS pretty much out-of-the-box so I am not familiar with options, but does this StackOverflow post work for you?

@teknowledgist
Copy link
Author

Ha! Twine-2.9.2-Windows.exe /S /ALLUSERS=1 did work! Many other installers use /ALLUSERS, but usually that is documented or returned with a /?.

I still think a silent install should default to an all-users/machine install, but I can do what I need, so thanks!

@klembot
Copy link
Owner

klembot commented Sep 18, 2024

Good to hear this resolved it. I'll repurpose this as a documentation task.

@klembot klembot changed the title Document or create option for silent, machine-wide Windows install Document options for Windows intaller Sep 18, 2024
@klembot klembot changed the title Document options for Windows intaller Document options for Windows installer Sep 18, 2024
@klembot klembot added the P3 (could) Annoying bugs that have workarounds, Interesting ideas label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P3 (could) Annoying bugs that have workarounds, Interesting ideas
Projects
None yet
Development

No branches or pull requests

2 participants