Ticket #587 (closed: fixed)
Fix problems with Mantid and installations in non-writable locations
Reported by: | Martyn Gigg | Owned by: | Martyn Gigg |
---|---|---|---|
Priority: | major | Milestone: | Iteration 19 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
Currently all output from Mantid gets put into the executable directory. If however, this is not writable then certain features will not work i.e. Python scripting
Change History
comment:4 Changed 11 years ago by Nick Draper
- Milestone changed from Iteration 17 to Iteration 18
Moved as part of iteration end
comment:6 Changed 11 years ago by Nick Draper
- Milestone changed from Iteration 18 to Iteration 19
Moved as part of iteration 18 end
comment:10 Changed 11 years ago by Martyn Gigg
- Status changed from new to closed
- Resolution set to fixed
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 1435
Note: See
TracTickets for help on using
tickets.
(In [2465]) Outputting files now differs under Windows and Linux. Linux now uses a directory under the user's home directory, $HOME/.mantid, to store things such as mantidsimple, logs, managed workspace files. This is basically so that the installation via the RPM can work properly. Windows behaviour should be unchanged. Re #587