AW: How do you grant executing rights to your app for all users?

Tiemo Hollmann TB toolbook at kestner.de
Tue Sep 30 04:03:50 EDT 2014


Hi Bill,
with chmod I set "rx" - read and execute rights. With the finder information
menu I only see the options to set "read and write" and "read only". How do
you set execution right via the info menu?
Tiemo


> -----Ursprüngliche Nachricht-----
> Von: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] Im
Auftrag
> von Earthednet-wp
> Gesendet: Montag, 29. September 2014 16:55
> An: How to use LiveCode
> Betreff: Re: How do you grant executing rights to your app for all users?
> 
> Tiemo,
> What I do is use the finder for this action. Single click on the app
bundle,
> use the menu at the top to "get info".  An info window comes up and there
is a
> little popup at the bottom where you can set access rights.  You should
then
> use the adjacent popup to make all files in the same folder have the same
> permissions.
> 
> Google is your friend. At least in this case.
> http://support.apple.com/kb/PH13799
> Bill
> 
> William Prothero
> http://es.earthednet.org
> 
> > On Sep 29, 2014, at 4:47 AM, "Tiemo Hollmann TB" <toolbook at kestner.de>
> wrote:
> >
> > Hello,
> >
> >
> >
> > When creating a new standalone, this standalone doesn't have executing
> > rights for other users on OS X.
> >
> > Everytime after creating the standalone I grant all users executing
> > rights with "chmod -R a+rx *" This works for me, but because my OS X
> > knowledge is very limited, I am interested, if this is the straight
> > forward way of doing it, or if I am missing something usual?
> >
> > In one of my programs the standalone is a kind of a splash screen with
> > some additional tasks and at the end I just go to a second stack,
> > which is part of my app bundle. Now I experienced by accident, that I
> > copied an updated version of this second stack into my finished
> > bundle. When starting with the admin user, everything worked fine. But
> > starting with a standard user, the splash stack just stopped at going
> > to the second stack without message or error. After some research I
> > found, that I forgot to execute the chmod again on my updated app and
> > it appears that even a non executable stack within a bundle needs
> > theses "rx" rights. Can you confirm this and is the manual chmod after
> > each standalone build the way how to do this, or am I missing something
more
> straight forward?
> >
> > Thanks for any insights
> >
> > Tiemo
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
subscription
> preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the use-livecode mailing list