Closed livecodestephen closed 10 years ago
I don't think lcVCS is the culprit here. What's the system umask and the directory permission?
Just to clarify. lcVCS does nothing other than put <data> into url "bin file:properties.json
etc...
My umask is set to allow executable permissions to be set, but that shouldn't mean that it will be set. I've tried a simple put
command and the file is created executable, so this looks like a LiveCode bug.
OK, thanks I'll let you follow it up internally but feel free to re-open if you think I should be setting the umask to 113 or something at the start and re-setting it to it's original value at the end.
To me, it certainly feels wrong that LiveCode defaults to creating executable files, but setting the umask would be the obvious work-around. I suppose this would also fix the problem in current and older versions of LiveCode.
I've opened Bug 12045 for the problem within LiveCode.
On export on linux every file has executable permission set. Note, this doesn't happen on OSX, so collaboration between the two OSes is difficult.