Yeah, I didn't like leaving the python script in /contrib, either, but I couldn't think of a better place for it. That's why I asked. :-)
As I read it, in order for a hook to fire, the shell script must live in the /hooks directory and must be named the same as the hook (e.g. post-commit). If I understand that correctly then it means that I can't have multiple shell scripts attached to a single hook (although the re may be multiple executables). All of the executable calls would have to exist in that same shell script. Does that help clarify? I'm just trying to confirm what I think I'm reading. On 7/25/06, Emmanuel Blot <[EMAIL PROTECTED]> wrote:
> 1. Is there any convention/best practice that indicates where a > post-commit hook script should be stored? It will work anywhere, I > know, but is there a recommendation? I personnally kept the Python script in the contrib directory because I'm lazy. I don't think this is the most appropriate directory ;-) > 2. Since the post-commit-hook file that gets executed lives in the > project's /hooks directory and must be named post-commit... You should have at least the shell scripts in the hooks directory of your Subversion repository, and these scripts should call the Python scripts wherever they are stored. > you can have multiple post-commit scripts executed just by calling all > scripts from that same hook file. Is there any problem with that or > is it done pretty regularly? I'm not sure to understand the question: "multiple post-commit scripts"? Can you elaborate? Cheers, Manu _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
-- Rob Wilkerson _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
