Wow, the ugliness of the real world raises its head, doesn’t
it? Thanks for rubyscript2exe and for handling this.
“In theory, there’s no difference between theory and practice.
In practice, there is.”
I guess I’m still uncertain what the difficulty is with a
sticky, world-writeable directory on the load path. Perhaps
there’s a subtlety I don’t understand. But once the file is
created, only the owner can remove or rename the file (due to
the sticky bit), and if the file’s permissions are otherwise
set correctly, no one other than the owner could alter it. So
where exactly is the vectory through which someone could do
I really don’t know. It’s a Ruby thing. Maybe Matz has the
answer. AFAIR, he changed his mind on this topic, several
And is it the case that when running an application created
with rubyscript2exe, that the SAFE level is greater than 0?
Because if it were 0 my understanding is it should at most
generate a warning and not an error.
RubyScript2Exe doesn’t change the SAFE mode of your application.
Erik V. - http://www.erikveen.dds.nl/