2012-05-31 05:32
|
rdesktop - fisk.bwh.harvard.edu_231.png (29,807 bytes) |
 |
Do you have any idea of what could be wrong ? This is also what I noticed ... I initially thought that the permission on the file were incorrect. |
|
2012-05-31 06:30
|
rdesktop - fisk.bwh.harvard.edu_232.png (178,571 bytes) |
 |
Looks like the file is not writable by users. Maybe the installer sets it up this way... |
|
|
Just created a small project allowing to do some experiment. See https://github.com/jcfr/TestCMakeFileInstall |
|
|
It resumes that even after explicitly setting PERMISSIONS associated with the install(FILES ...) statement. The installed file is still not writable. install( |
|
|
Since explicitly settings the file permission within the CMake install rule doesn't work as expected, the workaround associated with 4.1.1 release will consist in asking the user to explicitly update the permission associated with the file. Let's note that an extension should fail to be installed if the launcher settings is read-only. This is captured by issue 0002144 and has been targeted for 4.1.1. Setting the permissions programmatically has also been considered but this could resume to be problematic on windows 7 platform. See issue 0002053. Given the fact the release if due for June 1st, the manual update of permissions will be suggested. Finally, the ideal solution would consist in having user specific extension settings differentiated by version of Slicer. This is captured by issue 0002143 and is targeted for 4.2.0. |
|
|
Let's also note that setting file permissions has been fixed in 4.8.1. See [1] I believe the problem could also be avoided by running Slicer as administrator. |
|
|
Dear issue reporter, Good news :) Slicer developers SOLVED the problem you reported - YOU now need to VERIFY and CLOSE this issue. |
- Anonymous
