[MERGE] Updates to bzr_access

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> Russ Brown wrote:
> | John Arbash Meinel wrote:
> |> The attached patch was written by "j^" on IRC.
> |
> |> It basically fixes up the contrib/bzr_access script to properly work
> with
> |> bzr.dev, and improve the documentation to match reality. (You can only
> |> manage
> |> whole-repo access, not per branch, etc access.)
> |
> |
> | That's annoying. I was planning to use this to control access to certain
> | branches.
> |
> | I suppose the obvious answer to that is to make it work myself and
> | contribute back. :)
> |
> |> I've reviewed it, and it looks good to me. Anyone else want to second
> it?
> |
> |> John
> |> =:->
> 
> There is a blueprint open for what needs to be done.
> https://blueprints.edge.launchpad.net/bzr/+spec/acl-transport
> 
> Specifically, it would work similarly to our current Chroot transport.
> If I was
> going to implement it, I would create a choke-point function based on the
> relative path.

This is a good approach if ACLs are only intended to prevent write
access to certain branches.  Preventing read access is much trickier in
a shared repo.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFISBpe0F+nu1YWqI0RAm1zAKCB9MzmdiCJkF5l3EgynHrxIXLAvACdF0d5
Ow2xBMv1aPSW64xqOPzSt2g=
=LVDM
-----END PGP SIGNATURE-----