Setting eol-style property on post commit hook

Hello Guys,

Though i have come across some threads which talk about this issue but they
being relatively old, i thought to check again..

So basically i want to set an eol-style property to native for all my text
based files. I will be enforcing this by making the developers/committers
enable the property "enable-auto-props" and accordingly set the file
extensions on which the property is applied in their subversion/config file.

BUT at the same time for users who mistakenly (or carelessly) dont set the
property, i would want to have a script executed on post-commit hook on the
subversion server.

Now i have following questions/concern

1) Is it a good idea to set the property using a script invoked on a
post-commit hook ? What implications can it have. In certain threads people
have suggested to rather have a strategy where the commits are rejected if
the property is not already set. Why is such an approach suggested over the
first one ?

2) Now, If it is ok to have such script, would the script require doing an
svn update and (after svn propset to eol-style) a commit again ?, cant we
just update the property on the actual files without the need to
synchronizing them and doing another commit (since that i believe would
introduce another revision just for setting the property), given the hook be
running on the same machine..

Thanks in advance and Regards

-- 
View this message in context: http://www.nabble.com/Setting-eol-style-property-on-post-commit-hook-tp16264145p16264145.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org