Exiv2 bug reports

[Gilles Caulier]

As i know, Robin has planed to move Exiv2 code to github, or something in
the team. I don't know exactly.

But the problem is more complex than that.

Few month ago, seeing all the problem in digiKam due of bad video support
in Exiv2, i proposed to Robin to revisit the Exiv2 code, using the same
technics used in digiKam :

1/ Pass all the code to static analyzer and fix the dysfunctions.
2/ only give the minimalist visibility of Exiv2 implementations from client
side, to prevent to break the binary compatibility of the library.
3/ Clean up code to permit to install more than one version at the same
time on a computer. I know serious problem in this kind of situation. This
is very problematic.
4/ complete cmake port and remove the automake/autoconf, to limit code to
maintain.

None of this points have been accepted. I insisted by Robin start to use
weird words about me.

Recently, after to report as UPStream some dysfunction, the bugs have been
rejected as well. Robin said that digiKam is a monster badly implemented
which perturb tha Exiv2 project.

Following this state, you can understand me to still polit, and left to
support Exiv2, and especially Robin ad the way trying to work in open
source. I have nothing to said to someone speaking to me like this.

Voilà, the problem is more human than technical... It's like in the real
life.

Gilles Caulier


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

> Le 09/04/2017 à 22:44, Gilles Caulier a écrit :
>
>> 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...
>>
>>
> reading the post it looks like the author is ready to do the task, may be
> needs only support and infrastructure?
>
> did you contact him directly?
>
> sorry, I'm in no way able to help you on programming :-(
>
> jdd
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170409/a1305079/attachment.html>