1) "Archive corrupt, unable to decompress"! (with Stuffit Expander 5.1) 2) "mozilla-mac-SeaMonkey_M3_BRANCH.sea.bin" Mac filenames are still limited to 31 characters, this ain't it!

Chris -- are you the one who should recieve this one?

Reassigning to Leaf. 1) There were compatibility issues with StuffIt Expander 5.x when attempting to expand archives created with StuffIt 4.x tools. I don't remember the particulars. Please see www.aladdinsys.com for update and compatibility information. 2) Yes, Mac's are limited to 31 chars. This should be shortened.

Can't users rename the file as they download it? The binary naming conventions are useful for us to keep track of what binaries do what and which branch they came from. mozilla-mac-m3.sea.bin will do, i suppose. I'll do this for m4. We'll make m4 a .sea, so we don't have to worry about what tools the user has (if we have a licensed copy of stuffit, of course).

1) "Corrupt archive" cyeh - compatibility problems were the other way around, users of Expander 4.x couldn't expand 5.x archives leaf - archive was already a .sea, the problem wasn't the compression, the problem was in the macbinary, the macbinary coding was corrupt Solutions: cyeh - program called MindExpander (available from download.com) will still expand bad archives as best as possible leaf - use binhex coding, far more standard among Mac users, has more redundancy built in, and is 7-bit safe (MacBinary isn't) 2) File name length leaf - yes, we can rename files when we download, the question is, "Why should we have to?" After all, you're trying to create something that improves your user's lives Solution: leaf - while "mozilla-mac-SeaMonkey_M3_BRANCH.sea.bin" is useful, something along the lines of "mozilla-mac-seamonkey-m3.hqx" still contains all the info and only logs 28 characters

Reassigning to jj; he's doing the mac deliveries to mozilla.org now.

cyeh, can we get an "M" for this? will you guys fix by M4?

This is something that should be fixed when M4 is complete.

ok, here's the story: 1) file name length. Daily builds pushed to mozilla.org (under mozilla/nightly) are always named "mozilla-mac.sea.bin". We made a mistake when renaming the "shipping" M3 bits and this will no longer happen for further milestones. Like <absinthe182@hotmail.com> suggests, we will use something like "mozilla-mac-M4.sea.bin" for such deliveries. 2) file encoding: MacBinary II format has been chosen by Netscape over Binhex a long time ago, for the following reasons: - nowadays, Internet pipes support 8-bits almost everywhere, and we never received any complaint about not using a 7-bit encoding method - .hqx files are somewhat 20% bigger than .bin files, which can be quite significant for 10MB+ files like ours. - unlike Binhex format, MacBinary II preserves "custom icons" which is another reason why we adopted it. (there is no custom icon yet for seamonkey, but it will eventually happen) Marking as fixed.

Marking Verified/Fixed.