On 14/11/20 12:06 am, Stille wrote:
From what I've been following the issue, it's a problem of some of the
exiv2 maintainers fearing legal repercussions. These legal
repercussions don't seem to actually be very likely, but this is still
something that needs to be hashed out in exiv2's kitchen before
darktable can do anything about it,
We might be seeing some movement on this. See
https://github.com/Exiv2/exiv2/issues/1229#issuecomment-727190658
so posting on darktable-dev about how darktable developers are being
overly cautious isn't going to help - it isn't *them* blocking this.
The email-Canon solution was tried already, they answered with some
non-commital
we-can't-invest-resources-in-this-but-aren't-saying-anything-about-you-doing-so-either,
the exiv2 hardliners were apparently not satisfied, and the story
continued...
I suggest the exiv2 bugtracker if you'd like to keep an eye on what's
going on https://github.com/Exiv2/exiv2/issues/1229 . Once they manage
to sort out these issue, the codefix is apparently quite simple (and
has been implemented by some users in their private copies of exiv2,
apparently) so it shouldn't be long until it shows up in exiv2, and
then darktable will likely not take too long either.
I'm sure some of the darktable devs can better describe just how much
work would be to use libraw in parallel to exiv2 - I'm not an expert,
but I believe the two aren't exactly isomorphous.
Hope this helps,
Ruxandra
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to
darktable-dev+unsubscr...@lists.darktable.org
--
David Houlder
+61 2 6248 7463
da...@davidhoulder.com
https://davidhoulder.com
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
