Exiv2 bug reports

[Gilles Caulier]

A fork is a possibility. Typically, i proposed to the rest of the team to
directly integrate Exiv2 core somewhere in digiKam core, with some part
removed that we don't use, as ssh and web support.

Forking Exiv2 will be not simple to maintain. Even if all the image support
is well implemented in Exiv2, there are always tags list to improve. For
the video support a lots of code need to be review and stabilized. So, it's
a long work to do, and we have also a lots of bugs to fix in digiKam.

So the decision is not simple to take. I'm shared...

Gilles Caulier

2017-04-09 22:31 GMT+02:00 jdd <jdd at dodin.org>:

> Le 09/04/2017 à 20:17, Gilles Caulier a écrit :
>
>> I'm back to this subject.
>>
>> I receive a mail from Exiv2 forum few days ago. This become more and
>> more critical for the future of Exiv2 :
>>
>> http://dev.exiv2.org/boards/3/topics/2829
>>
>> I don't know where is the problem exactly in Exiv2 team. Even if Exiv2
>> 0.26 is released, i fear to see a very long time before a next 0.27
>> release with video support bugfixes, as i hope.
>>
>> So we need a solid alternative...
>>
>
> isn't this a call for a fork?
>
> jdd
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170409/93d69945/attachment.html>