Open teknowledgist opened 2 months ago
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.
@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?
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!
Good to hear this resolved it. I'll repurpose this as a documentation task.
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