It's pretty weird...  it seems like there's a directory with the same name as the VM that contains the VM:

Lumi-4:~ schwa$ cd /Users/schwa/Squeak/images/pristine/Squeak4.1.1-mac/Squeak\ 4.2.3beta1U.app 
Lumi-4:Squeak 4.2.3beta1U.app schwa$ ls
Squeak 4.2.3beta1U.app	__MACOSX

If I look inside the inner Squeak 4.2.3beta1U.app, it looks like a normal OS X Squeak VM (eg: the actual executable is inside in "Contents/MacOS/Squeak VM Opt").  When I try to run the inner VM, it works fine.

Not sure how this could have happened.  Perhaps the unzipper created a directory with the same name and unzipped into that?

Cheers,
Josh


On Apr 11, 2010, at 3:55 PM, Lawson English wrote:

> Andreas Raab wrote:
>> On 4/11/2010 8:41 AM, Lawson English wrote:
>>> Andreas Raab wrote:
>>>> Folks -
>>>> 
>>>> I just finished rc3 for the 4.1 release and unless I'm missing
>>>> something this is probably "it". It feels solid, there are no pending
>>>> issues and consequently I'd like everyone to treat this as if it is
>>>> the release. Download it here:
>>>> 
>>>> http://ftp.squeak.org/trunk/4.1rc3
>>>> 
>>> 
>>> A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM
>>> included in the Squeak4.1.1-mac.zip is damaged.
>> 
>> Ouch. Damaged? In what form? The build process simply extracts the VM and puts it into the same directory. Is this a permission issue perhaps? (i.e., do I need some or all of the VM to be executable when I make the build?)
> Haven't looked into it further. Just the icon is grey on my mac. Double clicking informs you its damaged. The same file sitting outside that zipped directory works just fine.
> 
> Lawson
> .
> 
>