Managing a photo library with bzr

[Sébastien Barthélemy]

2008/7/28 John Arbash Meinel <john at arbash-meinel.com>:
> | I would like it to be versioned, and thus I'm wondering of bzr would
> | be suited for that.
> | To give you an idea, I currently have 6100 pictures, "weighting"  7,2 Go.
>
> So, there are a few questions about why you want it to be versioned,
> etc. Are you modifying the pictures, such that you want to be able to
> get back to an older version of them?
> Is this *really* better than a real backup system?

Indeed yes. However for most pictures, modifications only happen on
the metadata, and I don't think they are compressed.
I like the idea to track the pictures, which is what bzr does. But
well, bzr does much more and it seems that it is not as suited as I
hopped.

> I don't think bzr is specifically well suited to the task. If you have
> some development ability in you (as you are at least writing python
> scripts to manage it), we would be open to patches which make things
> work better for you. (Subject to the standard: are of good quality,
> don't reduce test coverage, don't reduce code clarity, sort of constraints.)

Thank you for all those comments. I will follow your advice and
dismiss bzr for this. However I still need to keep an history of the
modifications.

Do you think RCS or SVN could do the trick ? I could also compute and
store deltas by myself, but I would prefer a widely used tool.

Thanks again