Ticket #1579 (closed: fixed)
Rename directory for mantid configuration
| Reported by: | Peter Peterson | Owned by: | Michael Reuter |
|---|---|---|---|
| Priority: | blocker | Milestone: | Release 2.6 |
| Component: | Framework | Keywords: | PatchCandidate |
| Cc: | nick.draper@… | Blocked By: | |
| Blocking: | Tester: | Peter Peterson |
Description
On linux, the mantid configuration is currently in ~/.config/ISIS/MantidPlot.conf, it should be ~/.config/Mantid/MantidPlot.conf.
Change History
comment:1 Changed 10 years ago by Nick Draper
- Owner set to Peter Peterson
- Status changed from new to assigned
- Component set to Mantid
comment:2 Changed 10 years ago by Peter Peterson
- Milestone changed from Iteration 25 to Iteration 26
comment:3 Changed 10 years ago by Peter Peterson
- Milestone changed from Iteration 26 to Iteration 27
comment:4 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 27 to Iteration 28
Bulk move of tickets at the end of iteration 27
comment:5 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 28 to Iteration 29
Bulk move of tickets at the end of iteration 28
comment:6 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 29 to Iteration 30
Accepted and assigned tickets moved at iteration 29 code freeze
comment:7 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:8 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:9 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:10 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:11 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:13 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.5 to Release 2.6
comment:14 Changed 7 years ago by Michael Reuter
- Owner changed from Peter Peterson to Michael Reuter
- Status changed from assigned to accepted
- Priority changed from minor to major
comment:15 Changed 7 years ago by Michael Reuter
This is a duplicate of #3417, but has no work on it, so I'll use this ticket. I think I've found a way to do this fairly simply. I will check this on all OSes and I don't plan on pushing this into develop any time soon.
comment:16 Changed 7 years ago by Michael Reuter
Refs #1579. First cut a swapping of config directories.
Due to the way Qt deals with the settings files, the swap must occur on shutdown.
Changeset: 7bc72c1dc30805625acc9e84db09650f7ee9a7fc
comment:17 Changed 7 years ago by Michael Reuter
Refs #1579. Putting settings switch back.
Changeset: b6cedcae97bcba8daf4953cc8d1e0f9293bd8d0e
comment:18 Changed 7 years ago by Michael Reuter
Refs #1579. Handling Windows registry copying.
Changeset: 0083e4046479816b54b2dad2af6580dcce0388ef
comment:19 Changed 7 years ago by Michael Reuter
Refs #1579. Remove debugging.
Changeset: d9145ef29ced4a546641753401d53f6da0f0a953
comment:20 Changed 7 years ago by Michael Reuter
Refs #1579. Make comments commensurate with new config location.
Changeset: b987e7234673f6be63c01581797664d5f5459a85
comment:21 Changed 7 years ago by Michael Reuter
Refs #1579. Adding documentation for function.
Changeset: d9eaf8fbbcb04ebab2c4a0264bca16bab63b3f46
comment:22 Changed 7 years ago by Michael Reuter
I think I have something that now works on all three platforms. However, we need to discuss deployment of this feature. If someone mixes running the release and the nightly/unstable versions, when they go back to the release version, none of their settings will be there.
comment:23 Changed 7 years ago by Michael Reuter
- Cc nick.draper@… added
- Priority changed from major to blocker
- Status changed from accepted to verify
- Resolution set to fixed
Branch is here.
NOTE: This ticket should not be tested without Nick's explicit consent as the changes contained here could have serious consequences for users if it gets onto develop or master. It will need to wait until release time to be checked.
To Test:
- Before running git test start 1579, run MantidPlot and observe the current configuration.
- Now, begin the testing phase.
- Startup and shutdown MantidPlot. This instance will have no configuration. On shutdown the configuration information will be shifted.
- Startup MantidPlot again and all of the configuration observed in 1. should be observed.
On Linux and Mac: The .config/ISIS directory should now be gone and replaced by .config/Mantid
On Windows: The registry entry ISIS/MantidPlot should be empty and the Mantid/MantidPlot should now contain all the config info. I was unable to figure out how to delete the ISIS entry.
Steps 3 and 4 will have to be done by users and explicitly spelled out in the release notes.
comment:24 Changed 7 years ago by Alex Buts
- Status changed from verify to verifying
- Tester set to Alex Buts
comment:25 Changed 7 years ago by Alex Buts
- Status changed from verifying to verify
- Tester Alex Buts deleted
I can test it but indeed it is better to wait until release time.
comment:26 Changed 7 years ago by Peter Peterson
- Status changed from verify to verifying
- Tester set to Peter Peterson
comment:27 Changed 7 years ago by Peter Peterson
This works as advertised for me as well.
comment:28 Changed 7 years ago by Nick Draper
Release notes have been created and note added, go ahead and merge to master. Announce to the dev team once complete. Ask dev team members to inform any users that they know are using the nightly build.
comment:32 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.5.4 to Release 2.6
Returned to Release 2.6 as patch release 2.5.4 will now not happen.
comment:34 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 2426
