Boinc(Manager) application installation location changed on macOS (8.2.?)

[brian163]

Can anyone tell me where it is documented that the macOS installation of the BoincManager application was moved to /Library/Application Support and in what version? I upgraded from 8.2.5 to 8.2.8 today and found my previous aliases and scripted paths broken. I discovered the Boinc(Manager) app was replaced in /Applications by an alias to /Application Support/BoincManager. Which to my knowledge is also not an Apple endorsed installation location for applications.

I'm guessing this switcheroo may be the basis of a fix for the long outstanding installation/upgrade permission issues but this strikes me as a very non-standard way of dealing with it. I looked through as many release notes as I could and did not find this documented as to being intentional or an actual explanation of the intent.

This also leaves various Wiki and documentation pages here outdated, which clearly state that the Boinc Application is installed in /Applications on macOS.

Thanks for any shared insight.

[CharlieFenton]

@brian163 Thank you for bringing this to our attention. The change was done in BOINC version 8.2.6. Unfortunately, the mention of this is a bit hard to find. The release notes have a link to PR #6616, which in turn has a link to PR #6609, which explains the reason for the change here.

After reading your question, I have updated the instructions for moving the BOINC Manager to a different drive so it reflects this change. I will ensure that it is mentioned in the ReadMe file for future releases.

I upgraded from 8.2.5 to 8.2.8 today and found my previous aliases and scripted paths broken.

I'm unclear that the move of BOINCManager.app in 8.2.6 and later caused this. Since the BOINC installer always replaces /Applications/BOINManagre.app it has always been necessary to repeat the procedure described in the above mentioned instructions after running the BOINC installer. I have updated those instructions to emphasize that.

If you think I've missed something here, or if the updated instructions don't work for you, please let me know so I can investigate further.

[brian163]

@CharlieFenton Apologies for my delay in response. Thank you for the response and the update to the documentation.

Brian