Juan,
I hate to bring bad news, but the updater bug still exists on my system. I tried the following:
1) Reinstalled PI and set all three permissions for the application to read & write
2) Ran Disk Utility and repaired permissions on the boot disk
3) Set all permissions to read & write for the boot volume, applications folder, user folder, and desktop folder
4) Moved PI to the desktop folder (permissions still the same -- all read & write)
5) Rebooted the machine
Same behavior when I launch PI -- updates are applied & downloaded, but on exit PI does not relaunch automatically, and when I manually launch it, the five updates are shown as pending. Moving the PI app to the Desktop or another volume (mechanical HD) does not matter, the updates are not applied.
Jim M.
Glad to know it works. That means your /Applications folder has some limited permissions that prevent the PixInsight updater program from writing the updates to PI's application bundle.
Although the standard location is /Applications, the PixInsight application can be run from any location on your filesystem. In fact, each copy of PixInsightXX.app is a completely independent and self-sufficient unit.
So far we have been working under the assumption that the user who launches the PixInsight Core application has full read/write permissions on /Applications. This is the default configuration in Mac OS X. However, this seems to be changing so we'll have to think on changing PI's update system on Mac OS X in the next version. Basically, it should work like the Windows version. On Windows, we rely on UAC (User Access Control) technology to request elevated privileges for the updater program. On Mac OS X we can use UNIX's SUID security for the same purpose.