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

[simon at margo.student.utwente.nl]

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





--- Comment #7 from  <simon margo student utwente nl>  2009-11-22 17:22:47 ---
Regarding HAL, I'm running ubuntu karmic koala and in the release notes it says
HAL is deprecated:

> hal deprecation
>
> Ubuntu 9.10 Beta's underlying technology for power management, laptop 
> hotkeys, and handling of storage devices and cameras maps has moved from 
> "hal" (which is in the process of being deprecated) to "DeviceKit-power", 
> "DeviceKit-disks" and "udev". When testing Ubuntu 9.10 Beta, please be alert 
> for regressions in those areas and report any bugs you find. 

So I suppose I should report this as a regression to ubuntu?

But the larger picture is still the one from my last comment, it's just not the
unix way to depend on meta-information about the storage device for this kind
of problems. If now HAL is deprecated and devicekit is used, in 5 years time
perhaps some other solution will be used, but the underlying philosophy is the
same old unix-way, so that's what you need to get things to work over longer
periods (and photo collections tend to be LONG periods).

So the problem is that some albumroots contain a different collection at
different times and digikam needs to differentiate between them?

The collection contains the actual photo-files and nothing else?

And the database is stored (theoretically) in a separate location (found by
digikamrc configuration?)

(In my case the digikam4.db is in the same toplevel directory as my collection)

Doesn't it make sense to add a collection identifying file to each collection's
root directory? That way you'll always know which is which. And even if you
want to solve the problem using some arbitrary other route (like uuid), there's
always a backup way to retain a working system.

Cheers

Simon

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