Ask HN: Should I create a file-and-metadata-oriented version control system?
There already exist many version control systems for managing source code. I've used a couple myself (Subversion and Bazaar) for my programming projects. However, I've also tried using them to keep non-code-related data and projects under version control. Some examples of such data would be a directory full of images, or articles, or e-mail mailboxes (such as Thunderbird's), or a directory on a web hosting account. I've wanted to track much of these files' metadata (timestamps, modes, owners, permissions, etc.) and be able to restore old files AND their metadata when desired. I've tried using Subversion and Bazaar for this, but they don't seem to make it easy to record, version, and/or restore files' metadata (assuming that's even possible with these tools). Furthermore, I'd like to keep directories I track clear of any revision control tools' own data (such as .svn or .bzr directories). (There are other features I'd like such a system to have, but we can cover that later...)
To reiterate, my two questions are:
1) Does such a file-and-metadata-oriented version-control system already exist?
2) (Assuming that the answer to question 1 is "no" or "not a good one"...) Is anyone else interested in such a system? I'd love to create it anyway for my personal use, but I'd be even more motivated if it'd also be useful to others. If so, I'd love to get in touch with potential users, as well as reading the experiences of others who have tried using a source-code-oriented VCS to track general files and directories (especially if they're not fully satisfied with the results).
Thanks in advance.