Importing TpQtLogger into our repos

George Kiagiadakis kiagiadakis.george at gmail.com
Tue Jan 31 14:36:42 UTC 2012


On Tue, Jan 31, 2012 at 3:12 PM, Dario Freddi <drf54321 at gmail.com> wrote:
> 2012/1/31 George Kiagiadakis <kiagiadakis.george at gmail.com>:
>> Regarding the API, I wouldn't consider it so stable. First of all, it
>> is based on QtGLib from QtGStreamer, which is not yet meant to be
>> public for other libraries. I never liked the fact that it was used in
>> tp-logger-qt, but that was the fastest solution back then. Soon (I
>> hope) QtGStreamer is going to move to the new GStreamer 0.11/1.0
>> series, which effectively means breaking API/ABI and with this
>> opportunity I am probably going to change a lot of things in QtGLib as
>> well to improve it. It is most likely that QtGLib-based bindings will
>> from now on be generated from gobject-introspection data, so when this
>> happens the whole tp-logger-qt library will have to be refactored. In
>> addition, tp-logger-qt is bound to the API of the underlying tp-logger
>> library, so whenever that library breaks API/ABI, tp-logger-qt also
>> has to do the same. Given this restriction, I believe the versioning
>> should follow tp-logger's versioning, like it is done with
>> QtGStreamer. So, keep 0.2 as major version and release 0.2.1, 0.2.2
>> and so on until tp-logger bumps its major version to 0.3, etc.
>
> agreed all over. We should probably have a plan for that as well,
> today I'm trying to find out if upstream has any plan. Will you be at
> FOSDEM to discuss that, btw?
>

Unfortunately no. I have an exam on monday :@


More information about the KDE-Telepathy mailing list