Other uses for tree versioning systems

luna luna at bzh.net
Sat Jun 11 14:10:59 BST 2005


John A Meinel a écrit :
> Aaron Bentley wrote:
>>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.
> 
> Well, you need to have some way of getting back the metadata for
> "revision-612". You certainly could store the meta-data into the
> inventory XML, but that is a little bit more invasive.
> 
> I'm certainly not looking to have merge/etc work on the .bzrpermissions
> file. I just want to have a version of the meta-data for each revision.

In my opinion, in this use case, file permission are not metadata, but
just data we want to be versionned as other data (file's contents, etc.)






More information about the bazaar mailing list