Published a toy project that will be used to reproduce and fix the problem. See https://github.com/jcfr/2720-install-writable-file

Even after explicitly setting user/group/world read/write permissions [1], file is not installed with appropriate permission.

[1] https://github.com/jcfr/2720-install-writable-file/commit/da9cf93765d15a588e175be95b745b6ed157d292

Will have to investigate how NSIS could be tune directly. May be signing the package could help. See [2]

[2] http://stackoverflow.com/questions/10581570/setting-the-uac-publisher-field-for-a-nsis-installer

Confirm/Check if extension works anyway

Waiting to get the verisign key that will allow to sign the application / package

I tested on a different windows 7 machine (not the one where I changed the permission of the settings file).

I can confirm:

1) that the error message about not being able to write to the settings file does still occur when installing an extension.

2) that the extension works in spite of the error message.

Given that the desired functionality works, perhaps it's better to either (a) avoid changing the permissions on the settings file since it requires signing the app or (b) store the information about extensions in the user's local data store. An advantage of (b) is that different users on the same machine could have their own extension installed.

Thanks for checking.

For simple extension, having the launcher settings updated is not an issue. Indeed, the required paths are set by the application:

• python path are set by updating sys.path
• path where the library located in the same directory has module are loaded thanks to the help of ctkScopedCurrentDir. See [1]

Keeping the path updated within the launcher settings has the advantages of providing an easy way to find out which paths are used and allow to start terminal with the proper environment.

For more complex extension (I am thinking about SlicerRT), not having the launcher settings updated is probably an issue since path containing additional libraries are not set by the application. (/path/to/module/lib/Slicer-4.2/)

Finally, let's note that having per user launcher setting is captured by issue 0002143. The idea, would be to keep the path settings in one file that would be used by both the launcher and the application. (On mac there are no launcher but the path could be read from a launcher settings file). It would bring consistency.

Our sysadmin Matt should provide me with the key to sign both app and installer later today.

[1] https://github.com/Slicer/Slicer/blob/master/Base/QTCLI/qSlicerCLIExecutableModuleFactory.cxx#L54

Considering that:

• extensions work on windows despite of the message
• certificate has been ordered and should be available in the coming two business days.

I re-targeted the issue.

Fixed in:
trunk: http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21482
4.2 branch: http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21489

Closing resolved issues that have not been updated in more than 3 months

Fix committed to 2145-support-for-installing-extension-from-file branch.