|
Edited on Fri Jun-30-06 10:32 AM by htuttle
I've written a few shareware and freeware programs. One day, I started getting a MOUNTAIN of email from new users that none of my programs would run after downloading them (which was odd, since they'd previously been fine). Many other shareware and independent software authors experienced the same thing with their own software distributions.
Turns out, Stuffit Expander 8.0, in a lame attempt to be 'secure' on OSX, removed the executable bit from all files it unstuffed. This meant that if you stuffed an application, it would not run when you unstuffed it with Expander 8.0.
Then along came Stuffit Expander 8.1 (which was the last version actually bundled on OSX, IIRC), which 'fixed' this problem by making EVERY file executable when you unstuffed it. Yikes.
At that point, I kicked Stuffit to the curb and used only DMG disk images for distributing applications. The biggest disadvantage with DMG files (other than being Mac-only) is that many webservers don't know what 'dmg' files are, and tend to omit sending the proper MIME type that causes the file to be downloaded. Therefore, you end up with the contents of the DMG file displayed in your browser window rather than downloaded to your hard drive (unless you do the control-click 'Save Link as' thing). Zipping the DMG prevents this, even though it doesn't really make the file any smaller.
The only other problem with DMG-based distributions is that an amazing number of users seem to be just baffled by the concept of DMG files. One root of this problem is that a DMG disk image is sort of a metaphor for a virtual floppy disk. Thing is, Macs haven't handled floppy disks for many, many years...it's an unfamiliar metaphor for a new user.
Now that zip file handling is built into the Finder, and seem to handle permissions and resource forks properly, I'll probably use ZIP for anything I distribute in the future.
|