[PATCH] bzr tracks permissions

[John A Meinel]

John A Meinel wrote:
...
> I haven't figured out how to include the information that permissions
> have changed. Also, it is certainly likely that some things like
> owner/group should not be committed all the time. (It means that when
> you do an rsync of mainline, it will look like every file has changed
> since it has a new owner & group).
> 
> Mostly I just wanted to get this patch out to get some feedback.
> Especially how to handle user/group issues.
> 

The specific issue that I am trying to determine, is how to take the
high-level information of "this branch should track owner/group
permissions info" into the low-level "does this InventoryEntry == other
InventoryEntry".

>From my cursory inspection of the code, in bzrlib/diff.py you only have
Tree objects (not Branch). So that would make the
"should_track_permissions()" function be a member of the Tree.

So does that mean it should be a file, like '.bzrignore', or maybe even
part of .bzrignore, some meta-info line in .bzrignore which states
whether you want to track meta information for this tree.

I could keep the information somewhere under '.bzr/' and just have all
of the places that a Tree object gets created make sure that they set
(or unset) the "track_permissions" bit for that tree.

The only time we need to be aware of the users particular desire to
track the permission changes is during merge, so I'm not as concerned
about that.

If the actual meta-info is only tracked when the bit is set, then you
need a way to set the bit, and then do an update commit. Which is why
I'm thinking it should always track the meta-info, just only use it when
the appropriate bits are set.

Just some more thoughts on the subject.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050606/051e15f2/attachment.pgp