Store volume information in volume itself, not in configuration file

[harri]

Information about volumes should be stored inside the volume itself. This way it will be possible to support e.g. removable disks (that can be mounted in different locations at different times). Configuration file should include only information about possible mount points.

This will break backwards compatibility with previous versions.

Open questions:

• How to handle indexing of existing read-only medias like CD-ROMs?
• How to handle situation in which several photovault databases index subtrees of each other's volumes? Say for example that user indexes his whole home directory for his own use but wants later to add some directories to family's photo archive (some others may contain sensitive material...)
• Backwards compatibility & conversion from previous versions. Especially in situations in which same directory has been indexed to several Photovault databases (it will have different UUID i.e. is essentially different volume in each one)

[harri]

Started implementation in r841. Still more testing needed, also most of the open issues are not addressed.