-
Notifications
You must be signed in to change notification settings - Fork 167
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
only insert custom_conclusion
if the file ends in .nsi
#701
Conversation
@larsoner - this should fix the problems you saw in the MNE updates! |
Co-authored-by: Marco Esters <mesters@anaconda.com>
# Custom conclusion file(s) | ||
@CUSTOM_CONCLUSION_FILE@ | ||
|
||
#else |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is pretty fundamental change. To restore old behavior, our custom conclusion files will have to add !insertmacro MUI_PAGE_FINISH
, correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, that was always the intention IIRC, but this sneaked in. Otherwise you can't replace the last page (like the example tries to do), and you get two "Finish" pages which feels weird.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two finish pages may be desirable from a marketing perspective, but I do agree that we shouldn't force a default page. I'm all for more flexibility
Description
Closes #700
A non-nsi
conclusion_file
(e.g. a RTF file) would leak into the NSIS template, creating syntax errors.Checklist - did you ...
news
directory (using the template) for the next release's release notes?