;
>
> --
>
> Message: 1
> Date: Fri, 8 Jun 2012 21:59:28 -0400
> From: Mark Rada
> To: "MacRuby development discussions."
>
> Subject: Re: [MacRuby-devel] Appstore rules on symlinks
.org
>>
>> You can reach the person managing the list at
>> macruby-devel-owner@lists.macosforgeorg
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of MacRuby-devel digest..."
>>
>>
>> Today's Topics:
>>
Hi, obviously filing a bug has a broken link now so ...
- Apple indeed wants the Version to be A (or B) so macruby_deploy has to be changed. All exactly like Apple wants it to.
- I personally didn't succeed in doing so, so i decided to leave that to the pro's and have built a "by-the book ready-t
Yes, i have seen that .. i will do some tests to see if i can get a working app
with a symlink although a manual change did not succeed thus far .. either it
cannot find macgems (if i hack the binary with "A") or it just crashes because
it can not find "Current" through the simlink any more
an
macruby_deploy fiddles with the version symlinks on purpose. We changed it in
the past for app store guidelines at some point; you should be able to see it
in the history of macruby_deploy.
It would be fastest to just revert that change and see if that fixes things.
Though if Apple really want
Hi Rob,
I haven't had time to look into it, but hopefully Apple is not looking to
restrict versions within framework bundles to "A", "B", "C", etc. As for
"Current" not being a symlink, that does seem like a bug. Would you mind filing
it as such so that we don't loose track of it?
- Josh
O
Hi all,
it seems that the Appstore validation has sharpened its control (again) …
submitting an app now is rejected because the Macruby framework does not comply
to the official Anatomy of Framework Bundles … There should be a symbolic
"Current" resolving to "A" ... in the Macruby Framework thi
