Proposal: project hooks and policies

[Jesse Glick]

Jonathan S. Shapiro wrote:
> Problem: you have a project. You want to ensure that some project-wide
> policy (enforced by hooks) is maintained, and you want to ensure that
> certain extensions are present (perhaps your scripts rely on them).

It is indeed not straightforward. For the repository I work on it was 
necessary to insert code into the master build script to do some setup:

http://hg.netbeans.org/main/file/7acea67ce725/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/RegisterExternalHook.java

But it's a lot of work and people can get confused if they start running 
VCS operations on a fresh clone without first running a build.

> 2. The down-stream user's local path to the policy workspace may not 
> match yours.

I'm not sure exactly what you're getting at here, but note that I have 
submitted a patch (which has still not been applied) that lets you 
specify an extension in .hg/hgrc using a relative path, which will be 
resolved relative to the repository root.