https://bugs.kde.org/show_bug.cgi?id=415949
K D Murray <f...@kdmurray.id.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |f...@kdmurray.id.au
--- Comment #4 from K D Murray <f...@kdmurray.id.au> ---
Hello all,
I've hit the exact same issue as David, as I am now also using git-annex. Could
I please ask that his patch be applied (or a similar solution found). Using git
annex to manage photo libraries is fantastic, and having to `git annex unlock`
a whole directory before editing metadata is very frustrating. A "git annex
mode" check box in settings could be used to selectively enable this behaviour
if you are concerned with backwards compatibility.
I'll have a brief attempt at implementing this in the next hour or so, and if
successful I'll make a PR on gitlab/invent.
To recap: git annex stores raw files as symlinks to an immutable directory
(good, my RAWs won't change), with *.xmp stored as normal files (tracked by ye
olde git). Digikam *should* be able to write to e.g. library/IMG0002.CR2.xmp,
but refuses to as library/IMG0002.CR2 is an immutable symlink. Digikam
correctly *reads* metadata in this case, and will write to it if one does `git
annex unlock library/IMG0002.CR2` (which replaces the symlink with a copy of
the immutable content, i.e. makes the situation "normal").
Best,
kevin
--
You are receiving this mail because:
You are watching all bug changes.
