Interesting, I just tried the checkout using TortoiseSVN and the
permissions on my machine now match the developers:
C:\dev\tools600>ls -al NMAKE.EXE
-rwx------+ 1 robert.reeves Domain Users 45568 Jan 6 09:42 NMAKE.EXE
So, why is TortoiseSVN (version 1.2.6) checking it out "properly", but
my Cygwin SVN (version 1.2.3) is not?
TortoiseCVS ships with a cvs.exe executable. I was hoping I could just
put TortoiseSVN's svn.exe on my path before cygwin/bin/svn.exe, but it
doesn't seem to be in the install dir...
Thanks!
Robert
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Sent: Thursday, January 05, 2006 6:29 PM
To: Robert Reeves
Cc: users@subversion.tigris.org
Subject: Re: Setting the Execute Bit on Checkout
On Jan 6, 2006, at 00:38, Robert Reeves wrote:
> My BIOS developers store their compile time exe's in SVN. When I issue
> "svn co https://server/svn/path/to/source" my compile time exe's do
> not have the executable bit set. When my dev's "svn co", theirs is set
> properly.
> Mine:
>
> C:\dev\tools600>ls -al NMAKE.EXE
> -rw-rw-rw- 1 robert.reeves Domain Users 45568 Jan 5 16:58 NMAKE.EXE
>
> Theirs:
>
> C:\dev\tools600>ls -al NMAKE.EXE
> -rwx------- 1 joe.blow Domain Users 45568 Jan 5 16:58 NMAKE.EXE
I don't work on Windows, but on *nix and Mac OS X, if you want a file to
get the execute bit after checkout, you should have its svn:executable
property set (to anything). Subversion does not manage any other file
permissions (except maybe the writable bit when using svn:needs-lock),
so the difference between your machine and the other developer's machine
is caused by something other than Subversion.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 6 16:58:00 2006