[Monotone-devel] Policy branch implementation

[Timothy Brownawell]

net.venge.monotone.tbrownaw.policy-branches

A fairly simple policy branch implementation. It can't handle multiple
policies yet. It translates branch names in 'ls branches' (but isn't yet
plugged in to the other paths that deal in branch names), and has some
code for commit access rules (also not fully plugged in).

Should probably merge in nvm.experiment.encapsulation before doing
further work, and use different types for user-visible and database
branch names.

It uses a new hook get_projects, which returns a table of branch-prefix
= policy-branch-name pairs. At the moment it will complain if there is
more than one element in the table (Need to fix the places that use
app.get_project() first).

Eventually it should handle having multiple policies and translate key
names.


   net.venge.monotone.tbrownaw.sample-policy-1
   net.venge.monotone.tbrownaw.sample-policy-contrib-1
   net.venge.monotone.tbrownaw.sample-policy-experiment-1
   net.venge.monotone.tbrownaw.sample-policy-tbrownaw-1

Sample policy branches for this to work with. The first has nvm and a
couple of nvm.* branches, and delegates the nvm.contrib, nvm.experiment,
and nvm.tbrownaw prefixes to the other policy branches.

The hook it uses would look like this:

function get_projects()
   local projects = {
      ["nvm"] = "/home/tbrownaw/src/mtn-policy/_MTN/test-policy"
   }
   return projects
end

and the test-policy file mentioned there looks like this:

policy_branch_id "net.venge.monotone.tbrownaw.sample-policy-1"
administrator "address@hidden"

which is the same as the delegations/* files in the policy branches.

-- 
Timothy

Free (experimental) public monotone hosting: http://mtn-host.prjek.net