I posted earlier some links to discussions of problems that OS X
users are having updating various apps. Here's a further thought
after digesting what I've read.
I believe this is an OS X bug, pure and simple. The point seems
to be that if an app defines certain files within its package as
read-only, then -- even after the user has authenticated him or
herself in response to a prompt from the OS -- updating the
package will fail. This despite the fact that the same user is
able to blow the whole currently-installed package away with no
problem. That's just inconsistent.
The gretl package contains various files marked as read-only, and
I'm not going to change that. For example, it's natural that as an
ordinary user you're not allowed to change the data files from the
Ramanathan textbook (though you're welcome to save changed
versions under another name).
In earlier versions of OS X this wasn't a problem: the same rights
that allowed you to delete the entire gretl installation also
allowed you to overwrite that installation with a new version.
Apple needs to get its act together with regard to the Darwin
equivalent of "sudo" operations on Linux.
I don't mind putting a note on the web page for gretl on OS X
alerting users to the fact that they may have to delete their
previous gretl installation before updating to a new version, but
that's as far as I'm willing to go to cater to broken behavior of
the OS.
Allin