From: "Eric I." <rubytraining@...>
Date: 2007-04-14T00:45:06+09:00
Subject: Re: rubyscript2exe.rb question

I've experienced this same issue on OS X (10.4.9) using Ruby 1.8.6.
I've been able to verify it's not a problem using Ruby 1.8.2 on OS X
and that it's not a problem on Ruby 1.8.4 using Linux.  And I'm pretty
sure it wasn't an issue with Ruby 1.8.5 under OS X.  So my guess is
that it surrounds a change in Ruby made between 1.8.5 and 1.8.6.

My best guess is that Ruby 1.8.6. does not seem to be taking into
account the sticky bit.

The original message in this thread showed an error message indicating
the permissions were 041777.  My error message reports the same.  And
the "1" would indicate that the sticky bit is set.

I can verify that your workaround of setting TEMP to a non-world-
writeable directory worked.

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.

Thanks,

Eric