Re: Status of libkface & libkgeomap

[Friedrich W. H. Kossebau]

Am Mittwoch, 26. Oktober 2016, 09:49:53 CEST schrieb Andreas Sturmlechner:
> On Friday, 29 July 2016 at 22:48, Gilles Caulier wrote:
> > Andreas,
> > 
> > Same situation for libkgeomap. This library can be also moved to
> > extragear-libs as only kphotoalbum use it.
> > 
> > Best
> > Gilles Caulier
> 
> Just bringing this up again before 16.12 freeze for consideration. I'm
> obviously not the one to decide, and I'm not aware of the motivation behind
> making it part of KDE Applications initially.
> 
> libkgeomap recently got some commits,

Those commits were done by me, but only to bring the code up-to-date with 
current Marble code. Those commits do not change the fact that there might be 
no maintainer and only kphotoalbum be using it.

Cheers
Friedrich

Re: Status of libkface

[Andreas Sturmlechner]

On Friday, 29 July 2016 at 22:48, Gilles Caulier wrote:
> Andreas,
> 
> Same situation for libkgeomap. This library can be also moved to
> extragear-libs as only kphotoalbum use it.
> 
> Best
> Gilles Caulier

Just bringing this up again before 16.12 freeze for consideration. I'm 
obviously not the one to decide, and I'm not aware of the motivation behind 
making it part of KDE Applications initially.

libkgeomap recently got some commits, but libkface remains now untouched for 
almost a year. Which is not bad per se, but the review to make it build with 
opencv-3.1 is still pending. Or should I just merge it now to give it some 
testing until 16.12.0 release?

Regards,
Andreas

Re: Status of libkface

[Gilles Caulier]

Andreas,

Same situation for libkgeomap. This library can be also moved to
extragear-libs as only kphotoalbum use it.

Best

Gilles Caulier

2016-07-28 10:40 GMT+02:00 Gilles Caulier :

> Hi,
>
> Not from digiKam team. As Kphotoalbum still use it, the better place will
> be extragear as you propose.
>
> We currently study new algorithms and new codes with a student this
> summer. New code will be completely different and will still in digiKam
> core.
>
> Gilles Caulier
>
> 2016-07-27 22:00 GMT+02:00 Andreas Sturmlechner <
> andreas.sturmlech...@gmail.com>:
>
>> Hi,
>>
>> Obviously libkface is not a dependency of digikam anymore since porting to
>> kf5, it looks like similar functionality is now bundled there. One of the
>> last
>> commits it received > 9 months ago was OpenCV3 support, which already
>> needs
>> downstream patching to build with OpenCV 3.1 (released in 2015-12-21). A
>> review has been pending for some time:
>>
>> https://git.reviewboard.kde.org/r/126833/
>>
>> Is it still being maintained? Right now kphotoalbum (kf5-port branch)
>> depends
>> on it. I wonder if it better be put in extragear at some point, though?
>>
>> Regards,
>> Andreas
>>
>> ___
>> release-team mailing list
>> release-team@kde.org
>> https://mail.kde.org/mailman/listinfo/release-team
>>
>
>
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Status of libkface

[Andreas Sturmlechner]

Hi,

Obviously libkface is not a dependency of digikam anymore since porting to 
kf5, it looks like similar functionality is now bundled there. One of the last 
commits it received > 9 months ago was OpenCV3 support, which already needs 
downstream patching to build with OpenCV 3.1 (released in 2015-12-21). A 
review has been pending for some time:

https://git.reviewboard.kde.org/r/126833/

Is it still being maintained? Right now kphotoalbum (kf5-port branch) depends 
on it. I wonder if it better be put in extragear at some point, though?

Regards,
Andreas

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team