-
Notifications
You must be signed in to change notification settings - Fork 265
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
Pass command line arguments to downloaded installer #57
Conversation
Thanks for contributing! Unfortunately there were the following style issues with your Pull Request:
Please see https://github.com/agis-/git-style-guide (you can use This message was auto-generated by https://gitcop.com |
Thanks for contributing! Unfortunately there were the following style issues with your Pull Request:
Please see https://github.com/agis-/git-style-guide (you can use This message was auto-generated by https://gitcop.com |
In addition to GitCop’s stylistic comments (can you please fix the issues; see the style guide?), can you please also organize the commits a bit more logically (“make it part of sparkle namespace” is neither a self-contained commit nor explanatory message and shouldn’t be a separate commit in the first place)? I also have some additional comments:
Don’t take me wrong: I would LOVE to merge this in once the issues are fixed. But I can’t merge it as-is. |
Fixed issues, pushed! |
Hi! Let me know if you decided on sparkle:installerArguments tag, or if you have any other suggestions which are needed for merging. |
Apparently, nobody else gives a damn, so let’s use In short, technically speaking, the above is just about perfect — thanks a lot! Could you please respect the file’s formatting, though? I think you’re not seeing it locally due to your editor settings, but look at the d833742 diff at GitHub: it’s full of whitespace changes all over the place and other strange formatting inconsistent with not only the rest of the code but even itself (space after |
File formatting <= Sure, I will clean up tomorrow or the day after. |
Got a little time so I corrected the style issues, and also made variable names more consistent (no more 'updateArguments'). |
There is a new, optional <sparkle:installerArguments> tag which specifies command line arguments to be passed to the installer. This makes it possible to invoke it for silent installation. If no arguments are passed, wxLaunchDefaultApplication() is used to maintain compatibility with previous WinSparkle versions.
Pass command line arguments to downloaded installer
Merged, thanks! I also added documentation to https://github.com/vslavik/winsparkle/wiki/Appcast-Feeds#installer-arguments, feel free to update it as needed if I got anything wrong. |
You're welcome, thanks for merging! |
With this patch you can specify a sparkle:arguments tag in the appcast xml, and that will be passed to the downloaded executable. Intended typical use case is something like "/SILENT", see #21
Thank You for pulling!