You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Steve Wray <st...@catalyst.net.nz> on 2004/04/07 23:31:05 UTC

preserving filesystem properties

Hi there,
I would like to use subversion to manage directory structures in which 
file ownerships and permissions are important.

Re: preserving filesystem properties

Posted by Ben Collins-Sussman <su...@collab.net>.
On Wed, 2004-04-07 at 18:31, Steve Wray wrote:

> "Filesystem properties: each file or directory has an invisible hash 
> table attached. You can invent and store any arbitrary key/value pairs 
> you wish: owner, perms, icons, app-owner, MIME type, personal notes, 
> etc. This is a general-purpose feature for users. Properties are 
> versioned, just like file contents."

These are examples of names of properties that you *could* invent for
yourself.

Subversion doesn't preserve permissions or ownership information;  it
simply provides a generic metadata mechanism for users to exploit
however they wish.

Ben Reser, I believe, has written a script to do what you're looking
for:  when you run it, it "stores" filesystem metadata in the properties
before committing, and also has the ability to read the metadata and
apply it to the files again.


> I've tested this with file permissions as well; the only thing I've been 
> able to find is preserving executable perms. 

Correct.  The svn:executable property makes a file executable.  It's the
only sort of permission that svn can understand, because permissions are
inherently un-portable from one OS to another.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org