chmod and DOS vs POSIX paths

[brassrat]

The source control package i use at work is sensitive to the 'read-only'
attribute of Windows files.
prior to 1.7, the command 'chmod -w DIR/FILE' worked fine.
now, with 1.7, chmod -w FILE no longer sets the read-only attribute - i
guess because 
fortunately, there is a 'work-around': chmod -w 'DIR\FILE' (or chmod -w
$(cygpath -w DIR/FILE))
i.e., using a DOS path makes cygwin treat the file system as not having acls
and i guess that kicks in the old behavior.

Is this the only way to change the 'read-only' attribute on windows files?
Would it make sense for something like: chmod ugo-w DIR/FILE to set it?

-- 
View this message in context: http://old.nabble.com/chmod-and-DOS-vs-POSIX-paths-tp27307971p27307971.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple