To my understanding, it's a requirement in accordance with Apple's sandboxing
policies, if you want an executable to be able to make changes to files inside
the executable bundle. The way it's supposed to work, no application is allowed
to write or modify anything in the old location where the actual application
binary resides, but in the new location they can.
As an administrative user I am able to copy files to both locations, but
sandboxing is not about folder permissions. It's about executable permissions
and it's baked into the OS so no one can (ostensibly) change it.
That is my understanding at least. I've not dug in enough to know for certain.
Bob S
> On Mar 27, 2017, at 09:45 , Tiemo Hollmann TB via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>
> Hello,
> "Apple requires" - Is this only a "best practise" guideline or what will
> happen if you don't care? I have an old application just migrated to LC 8,
> where I am running an independent stack file in that old
> dir("Contents/MacOS"), and it is running fine on MacOS 10.12.3
> Is there any Apple link about that or are there any informations, into which
> issue you can run, if you put files into the old dir? If you integrate
> Valentina, they also keep one file in that directory.
> Thanks for any info
> Tiemo
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
