Other uses for tree versioning systems

[Aaron Bentley]

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

John A Meinel wrote:
| For my money, here is the basic layout: ($WD = the working directory)
|
| 	In $WD put a file ".bzrpermissions", this then becomes a version
| controlled location where permissions are kept up to date. It can be an
| XML file, which maps file_id => whatever set of permission bits you
| like. (Note: directories also have a file_id).

Personally, I think it's usually a bad idea to have your control files
be revision-controlled.  Since you know what they mean, you can do a
much better job of applying changes as part of the plugin than any
text-based merge algorithm could do.

| 	And updated cmd_merge() which after running the regular merge,
| 	can do a meta-data merge.

The merge/changeset application code is already highly pluggable.  You
just need a MyThreeWayPermissionMerge class that has an apply()
function.  You stick that in the ChangesetEntry.metadata_change fields
of affected entries.

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

iD8DBQFCqG+80F+nu1YWqI0RAmi3AJ9EPpbOg28qRt37zNAK77AmKazFFwCbBc2e
hmdN6sPXoqz90NARKNX00BQ=
=1Phj
-----END PGP SIGNATURE-----