[Digikam-devel] [Bug 215486] collection not found in location on disk with uuid (lvm volume)

simon at margo.student.utwente.nl simon at margo.student.utwente.nl
Tue Dec 22 07:44:13 GMT 2009


https://bugs.kde.org/show_bug.cgi?id=215486





--- Comment #13 from  <simon margo student utwente nl>  2009-12-22 08:44:09 ---
To me it seems like you're desperately set on using an API intended to get
details about hardware when you really want to put a label on a directory-tree. 

How do you handle:
- more than one collection on the same disk?
- moving a collection from one disk to another?
- moving a collection to another linux install?
- sub-collections?
- fixing a collection from a broken disk?

Say you put a file: .digikamcollection containing some information about the
collection like: owner, date of last access/additions, key for the digikamdb,
etc.

This would solve a lot of problems and it is doesn't get in the way.

Additionally, I think it would be a good idea to more pro-actively try to match
a physical collection to a collection in the database when a quick match (based
on uuid or the file I propose) isn't possible.

I hope you can see that the bug (as I intended it) isn't resolved at all!

/Simon

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list