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

subversion do not save filesystem permission... (fwd)

From: Roger Jorgensen <rogerj_at_nhn.no>
Date: 2006-05-16 15:41:40 CEST

anyone that have any idea howto fix this?

--
Roger Jorgensen <rogerj@nhn.no>
Installasjon og Drift
Norsk helsenett AS, Boks 6448, 9294 Tromso
---------- Forwarded message ----------
Date: Tue, 16 May 2006 15:21:59 +0200 (CEST)
From: Roger Jorgensen <rogerj@nhn.no>
To: sussman@collab.net
Cc: Roger Jorgensen <rogerj@nhn.no>
Subject: subversion do not safe filesystem permission...
i,
Bellow it s post taken from http://svn.haxx.se/users/archive-2004-04/0444.shtml 
where you say you have a script to preserv filepermission when you check files 
out of SubVersion. It would have solved one problem I have atleast where we use 
subversion to store alot of config files... but it cause issued since 
subversion don't preserv the original permissions.
From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-04-08 02:09:24 CEST
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
Received on Thu Apr 8 02:11:20 2004
       * This message: [ Message body ]
       * Next message: Philip Martin: "Re: Possible bug in keyword 
replacement (revisited, with examples)"
       * Previous message: John Aldridge: "Re: rcs $Log$ equivalent?"
       * In reply to: Steve Wray: "preserving filesystem properties"
       * Next in thread: andy.glew_at_amd.com: "RE: preserving filesystem 
properties"
       * Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject 
]   [ By Author ] [ By messages with attachments ]
This is an archived mail posted to the Subversion Users mailing list.
--
Roger Jorgensen <rogerj@nhn.no>
Installasjon og Drift
Norsk helsenett AS, Boks 6448, 9294 Troms
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 16 16:11:29 2006

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

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