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

Re: question about unix file permissions

From: Steve Wray <stevew_at_catalyst.net.nz>
Date: 2004-07-04 23:18:28 CEST

On Saturday 03 July 2004 11:44, Eric Wilhelm wrote:
> # The following was supposedly scribed by
> # Tim Alsop
>
> # on Friday 02 July 2004 05:42 pm:
> >I wondered if there were any plans to support unix file permissions
> > and ownership for files in the repository ? Currently when I check
> > out my build environment from subversion I have to modify all of
> > the shell scripts using 'chmod u+x' so that they are executable. If
> > it was possible to store permissions of unix files in the
> > repository this could be avoided. Any ideas ?
>
> I'm not sure about permissions in general, but you can have them
> executable:
>
> svn propset svn:executable 1 <svn-controlled file>

Yeah I've often wondered what this 'executable' property is supposed to
do cross-platform between windows and *nix boxes; if I have a script
marked executable on linux and it goes into svn with the executable
property and I check it out on windows what happens? Does it change the
extension? To what?
:)

Now what I'd like to see is autoprops applied to this sort of thing; I
already have a couple of perl scripts which create/update svn
properties to reflect filesystem mode, uid, gid (on Linux) but they
have to be applied by hand.

> I hadn't thought about this before your post. I've recently taken to
> using a 'new file' script which chmod's the file as 755 before doing
> 'svn add'. The files added in this way stay executable when checked
> out elsewhere, while those that have been chmod'd after being added
> don't.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 5 20:26:50 2004

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.