On Feb 24, 2009, at 06:00, A. L. wrote:
> I'm facing the problem of the change of the executable bit of files
> under version control.
> I red the manual and looked around the web and all I got is
> "svn:executable is automatically managed only during adds and
> imports".
>
> How to cope with subsequent "chmods"?
> At the moment, except remapping the chmod command itself and
> bringing it to perform the proper propset or propdel according to
> the chmod parameters that sounds a general bad solution, I cannot
> figure an automatic way to propagate changes of the executable bit.
I am not aware of an existing automated way to detect this. My advice
to you: When you want to make a versioned file executable, do not run
"chmod +x file"; instead run "svn propset svn:executable '*' file".
When you want to remove the executable bit from a versioned file, do
not run "chmod -x file"; instead run "svn propdel svn:executable file".
> I can also imagine a pre-commit script that checks all the
> executable bit of all versioned files and propsets svn:executable
> for all the executable files and propdels for all the others... but
> it's unapplicable for large file bases like the one I'm working with.
Not possible, because the pre-commit hook runs on the server but the
file with the executable bit is on the client. By the time the file
has been encapsulated into a transaction and sent to the server, it
no longer has an executable bit for the pre-commit hook to test.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1220419
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-24 13:13:40 CET