[Digikam-devel] [digikam] [Bug 347937] Collections added as "Removable Media" change as "Local Collections"

[RJVB]

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

--- Comment #4 from RJVB <rjvbertin at gmail.com> ---
(In reply to RJVB from comment #2)
> Hmm, if you can point me to where/how this is done in digikam's sources, I
> can have a look at Solid.

I can try to see what goes wrong in Solid when I know how it is being used by
digiKam.

> share. Why not store the information how a collection was added and use it
> as an additional property (or to override whatever Solid tells you on OS X
> and potentially other platforms where Solid dysfunctions)?

Collections are added as `Local`, `Removable` or `Network`, and treated
accordingly. Apparently this property isn't stored; instead you rely on Solid
to keep track of which collections are on local, removable or network storage.
If Solid isn't reliable in telling you if a collection directory is on local,
removable or network storage, you should store that property with the other,
non-hardware related properties (like the collection name).

This would probably also make it easier to work with temporary collections,
"scratch" folders that are on local storage but not always present. The same
could apply to collections on "fancy" filesystems: I have no idea how Solid
would recognise a ZFS pool or dataset for instance.

There's an underlying question of principles here: should you use technology to
second-guess the user, or should you just take it for given when s/he tells you
"this collection is on removable media, treat it as such"?

-- 
You are receiving this mail because:
You are the assignee for the bug.