[digikam] [Bug 377587] The --database-directory argument should also be the location of the digikamrc file when used

Simon bugzilla_noreply at kde.org
Wed Mar 22 11:34:25 GMT 2017


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

--- Comment #4 from Simon <freisim93 at gmail.com> ---
Ok I see your point and I completely agree, this is not an issue of
implementing, but of what behaviour do we really want. I am happy to change it
once we reach a consensus.

I will explain my point of view, but I am aware that it may be skewed due to
"knowing the inner workings":
In my opinion the behaviour should always be the least surprising. We have both
--database-directory and --config (I assume that anyone who actually uses
command line arguments is aware of this). For me the simplest and clearest is,
when both have just one purpose. With your proposal --database-directory has
the side effect of also changing the config location, which is (still, my
impression) not directly obvious. Database and configuration being separate
entities is common for many software.

My intended use case: I have two collections, one on the laptop and on a
network share. The databases are also stored on the laptop and on the network
share respectively. I want digikam to have the same behaviour no matter which
database I am using, so I share the config between the two.

About your use case: Information is always stored in the database. You can only
select whether you want to store it in image metadata/sidecar files as well.
Therefore I don't really understand your example, unless A and B manage the
same set of photos in the same location. But that would mean having different
information in the image metadata and the sidecar in the same location, which
seems very wrong to me in the first place (?).

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


More information about the Digikam-devel mailing list