OS X Installer annoyance.
I just noticed something potentially annoying about the .pkg
installer for OS X. If one moves the MaxMSP 4.6 folder to a location
other than its default, the installer will not update the files in
the new location. I organize my applications folder with subfolders,
and noticed I had two 4.6 installs, due to updating to 4.6.2, which
threw a new folder in to /Applications.
Im not sure what the official word is from Apple on how this all
should work, as some Apple application installers work properly when
moved from the default, and others do not. Is this possible to
implement? Not a huge deal, but it caught me by surprise, and it
would be nice if it could do it.
v a d e //
On 29 Sep 2006, at 23:10, vade wrote:
> I organize my applications folder with subfolders, and noticed I
> had two 4.6 installs, due to updating to 4.6.2, which threw a new
> folder in to /Applications.
This is actually the behaviour I want, at least some of the time – if
I have an old installation of Max/MSP which I’ve explicitly renamed,
I don’t want the installer to update it (especially if installing a
nick rothwell — composition, systems, performance — http://
> Im not sure what the official word is from Apple on how this all should
> work, as some Apple application installers work properly when moved from
> the default, and others do not.
Apples own installers all do it like that out of my experience, I must
not put iTunes into my music subfolder if I want it replaced…
It should be like that as Nick pointed out…
My solution is to never put any 3rd party external into the externals
folder, but always include an extra folder with that stuff into the