I agree there is no need to put the extra metadata in the /same/ data repository, as long as we can reliably link information between the two. I supposed it would be simpler to extend the current inventory than to implement a separate parallel one, but you know bzr better than I do :)
I still think it would be valuable to implement this in a reusable way : to merge the two proposals in one, how feasible would it be to implement a separate, generic metadata store that gets used if you provide the corresponding hook functions :
- get the metadata information from a file/dir/link
- set the metadata information back to a file/dir/link
- represent differences in metadata in a textual form
- ...
I agree there is no need to put the extra metadata in the /same/ data repository, as long as we can reliably link information between the two. I supposed it would be simpler to extend the current inventory than to implement a separate parallel one, but you know bzr better than I do :)
I still think it would be valuable to implement this in a reusable way : to merge the two proposals in one, how feasible would it be to implement a separate, generic metadata store that gets used if you provide the corresponding hook functions :
- get the metadata information from a file/dir/link
- set the metadata information back to a file/dir/link
- represent differences in metadata in a textual form
- ...