Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

3029: Do not use previous App directory and warn user when installing in existing directory #3042

Merged
merged 2 commits into from
Aug 21, 2024

Conversation

krzywon
Copy link
Contributor

@krzywon krzywon commented Aug 16, 2024

Description

This PR changes the INNO setup in order to always select a default directory (C:\Sasview-), not the previous one SasView was installed in and warns the user if the directory already exists.

Fixes #3029
Refs #3030

How Has This Been Tested?

I downloaded the Windows installer generated on push and tested both of the above items work.

Review Checklist:

Documentation (check at least one)

  • There is nothing that needs documenting
  • Documentation changes are in this PR
  • There is an issue open for the documentation (link?)

Installers

  • There is a chance this will affect the installers, if so
    • Windows installer (GH artifact) has been tested (installed and worked)

Licencing (untick if necessary)

  • The introduced changes comply with SasView license (BSD 3-Clause)

@wpotrzebowski wpotrzebowski added the SasView 6.0.0 Required for 6.0.0 release label Aug 21, 2024
@butlerpd butlerpd self-requested a review August 21, 2024 12:30
Copy link
Member

@butlerpd butlerpd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code changes look reasonable (not that I know much about INNO setup). This is unfortunately a place where the version number has to be updated separately from what is in the init file.

Importantly installing 5.0.6 then installing this PR the installer defaults to suggesting the sasview-6.0.0 folder not the previously installed folder. Install works. Installing again without removing 6.0.0 still defaults to the same folder but brings up a warning that the folder exists and asks if we want to proceed. Doing so works though that is because we are installing exactly the same files.

Unfortunately this does not address #3030. Installing on top of 5.0.6 for example does produce the warning (which it did before) but if the answer is "yes" the installation is completely broken and will not start (as before).

Ideally if the answer the user gives is "yes overwrite" we should remove the folder and recreate it. However the minimum should be to remove the option and just say we cannot install as the folder already exists.

Perhaps that should be another PR? I am approving this as fixing #3029 only as I'm guessing that was the intent?

@butlerpd
Copy link
Member

Never mind .. I see where indeed #3030 is being addressed separately. So this should be able to be merged.

@butlerpd butlerpd merged commit 65f24ac into release_6.0.0 Aug 21, 2024
28 checks passed
@butlerpd butlerpd deleted the 3029-default-install-directory branch August 21, 2024 14:08
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
SasView 6.0.0 Required for 6.0.0 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6.0.0b2 installer default folder is not 6.0.0 but whatever the last folder that SasView was installed to
3 participants