[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Fine-grained permissions on checked out files?

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2002-08-21 03:20:10 CEST

I'm currently playing with importing my home directory into SVN
and the one thing that I really need to have is being able to
declare a file as "read-only", "write-only" (of course, executable
is already present). And, I would also like to extend this to
the traditional Unix model of ugo. My umask wouldn't work as
each file has explicitly different permissions.

A property like svn:protection="600" which would then just call
apr_file_perms_set() would do the job (perhaps the octet values
wouldn't be the cleanest way, but it'd work). Of course, on OSes
where APR would return APR_INCOMPLETE or APR_ENOTIMPL, that would
not be treated as a fatal failure. But, at least the client has
enough knowledge to know what the right perms should be. (I'd
guess the default would be not to have this gathered from an import,
but allow the user to do a propset on this, but of course, we know
the original modes on an import or add.)

Of course, I'm willing to code this up, but before I do, I'd like
to throw it out there for any thoughts or concerns. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 21 03:20:44 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.