[Pharo 2.0] Mac installer package problems

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Pharo 2.0] Mac installer package problems

jtuchel
Hi,

I've just downloaded the mac installation package for Pharo 2.0 from http://gforge.inria.fr/frs/download.php/32303/Pharo2.0-mac.zip .

Then I just double clicked it to get it unzipped on Mountain Lion. The resulting .app cannot be started with a double click. ML says it is broken and should be moved to Trash. Opening it with Cmd-Click or a right click also doesn't work.

I can start it with the shell script inside the package, so this must be something related to OS X.

Has anybody seen this? Any known workaround?

Joachim
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 2.0] Mac installer package problems

Marcus Denker-4

On Apr 9, 2013, at 9:15 AM, jtuchel <[hidden email]> wrote:

> Hi,
>
> I've just downloaded the mac installation package for Pharo 2.0 from
> http://gforge.inria.fr/frs/download.php/32303/Pharo2.0-mac.zip .
>
> Then I just double clicked it to get it unzipped on Mountain Lion. The
> resulting .app cannot be started with a double click. ML says it is broken
> and should be moved to Trash. Opening it with Cmd-Click or a right click
> also doesn't work.
>
> I can start it with the shell script inside the package, so this must be
> something related to OS X.
>
> Has anybody seen this? Any known workaround?
>


Yes, there is a bug report:

10062 OneClickImage not working under OSX with case-sensitive FileSystem

it says:

The culprit is in the Info.plist

1:
2:
    <key>CFBundleExecutable</key>
    <string>pharo</string>

but the binary name should be uppercase <string>Pharo</string>


and yes, this should have already been fixed but was not…

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 2.0] Mac installer package problems

jtuchel
Marcus,

thanks for your fast response and for not answering with a RTFM - respectively the bug tracker ;-).
I am glad the thing is on the table and going to be fixed.

Unfortunately, I changed line 351 of the info.plist from  <string>pharo</string>  to  <string>Pharo</string>  and the problem persists... So there must be something more to do.

Joachim
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 2.0] Mac installer package problems

Marcus Denker-4

On Apr 9, 2013, at 9:33 AM, jtuchel <[hidden email]> wrote:

> Marcus,
>
> thanks for your fast response and for not answering with a RTFM -
> respectively the bug tracker ;-).
> I am glad the thing is on the table and going to be fixed.
>

I have chafed the templates in the git repository, so the next build
will pick up that change.

> Unfortunately, I changed line 351 of the info.plist from
> <string>pharo</string>  to  <string>Pharo</string>  and the problem
> persists... So there must be something more to do.
>

Hmm… so how can we find out what? For me they work fine.

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 2.0] Mac installer package problems

jtuchel
Hi Marcus,

I just tried disabling restrictions for starting Applications (Don't know the correct english name) in the security preferences to "No Restrictions" , and now I can start the Pharo.app by double clicking.

I previously had "Mac App Store and verified developers", and had the message pop up.

So the change to info.plist worked.

Funnily, now after I switched back to the old security setting, opening with Right Click as well as a double click works like a charm... I guess I will not be able to replay that situation ever again, unless I reinstall ML. Which I won't  ;-)

So again: thanks a lot. My issue could be solved. Not sure it will be solved for everybody, though. Let's see if others report the same problem...

Joachim
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 2.0] Mac installer package problems

Marcus Denker-4

On Apr 9, 2013, at 10:02 AM, jtuchel <[hidden email]> wrote:

> Hi Marcus,
>
> I just tried disabling restrictions for starting Applications (Don't know
> the correct english name) in the security preferences to "No Restrictions" ,
> and now I can start the Pharo.app by double clicking.
>

Ah, yes, we do not compile the binaries as signed applications…
We should do that.

        Marcus