Re: Windows SVN does't add svn:excecutable, which causes incorrect permissions for Cygwin Checkout

On 4/17/07, Dave Lawrence <dlawrence@ad-holdings.co.uk> wrote:
> If a file is added using a Windows build of SVN it does not have
> svn:excecutable property added. Therefore, if the file is subsequently
> checked out using Cygwin SVN, the executable permission is not applied
> to the file on creation of the working copy.
>
> Workaround:
> 1) Set the svn:executable property manually
> 2) Manually set the file permission in the working copy if necessary
>
> Suggested fix to Windows client:
> 1) svn:executable should be added automatically according to the same
> rules the cygwin client uses
> 2) Checkout behavior with respect to this should remain as it is
>
> Note: where the permissions are missing from dll files, this can cause
> "strange" bugs, instead of straightforward "permission denied" errors

There is no way a native Win32 build of Subversion should be setting
this property as it has no applicability to the Win32 environment. I
doubt that a Win32 client, upon checking out a file with this property
has any ability to run a Win32 API that could do anything relevant in
Cygwin.

If this is something you need in Cygwin, you should stick with a
Cygwin client exclusively.

I would not object if the auto-props feature were opened up in a way
that allowed this property to be set by that mechanism. That being
said, I think there are a lot of obstacles to overcome before that
could happen and I do not think it is worth it.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org