Jack Repenning wrote:
>> I don't understand why the files are being created read-only in the
>> first place in your situation, though. Does the mac have the
>> unix-like umask concept that you could change? Or is there some
>> mismatch between user ids on the client and server?
> Mac definitely has umask. OS X is just another UN*X.
> I think these files are normally read-only (by Subversion, to keep
> humans from inadvertently messing them up).
> The difficulty appears to be a difference between UN*X and Windows file
> system behaviors. Since (in the troublesome cases) the files are
> actually stored on Windows, or are accessed via SAMBA (which works very
> hard, and with quite laudable success, to pretend to be Windows), both
> file systems have to agree to allow the operation; but there is no
> agreement. I don't entirely grok the discussion I linked to, but I've
> encountered several similar miss-match problems in the past.
Conceptually, I think the difference is that on unix-like systems, the
ability to create and delete files is controlled by the permissions on
the containing directory. If you have write access to the directory,
you can delete a file regardless of the file's permissions. On windows,
where your files actually reside, I think you must have write permission
on the file itself - but unless this is set explicitly it would be
inherited from the directory above.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-03 20:35:40 CEST