Re: [Soprano-devel] Some additional Qt5 porting.

[Денис К. <den...@gm...>]

Hello!

When you have decided to make a release? Just interesting.

Best regards, Denis Kuplyakov.

2015-07-27 16:53 GMT+03:00 Денис Купляков <den...@gm...>:

> I don't know concrete date. The situation is that Calligra Author hardly
> depends on RDF with the new functionality (outliner). But the fact is that
> this outliner isn't finished, so I with calligra devs have decided by now
> to make RDF not to be a hard dependency and hide Outliner from users if
> there is no valid Soprano found during building of code. So I can say we
> will need new soprano released with a release of Author that will have a
> first version of Outliner. Outliner is my GSoC project and is planned to be
> finished at least by end of september, if there will be no other underwater
> stones (that was my previous GSoC too, but I didn't finished with it).
>
> And Friedrich W. H. Kossebau (calligra dev) recommends some renaming:
>
> Problem:
>
> macro_optional_find_package(Soprano)
>
> finds the qt4 version here. Which of course is the wrong version.
>
> (Uses the FindSoprano.cmake as installed with the kdelibs4 devel package)
>
> Best solution, very recommeded to invest into that:
>
> have soprano-qt5 install some cmake config files, and add a -qt5 postfix
> to the name, like done with other qt-using software for their qt5 variant.
> Then change the package find line to
>
> macro_optional_find_package(Soprano-qt5)
>
> or whatever name you will use for this variant.
>
> See http://api.kde.org/ecm/module/ECMPackageConfigHelpers.html for
> related macros to use with soprano perhaps, and see e.g. in kdesupport
> modules how they are used, e.g. in attica:
>
> http://quickgit.kde.org/?p=attica.git&a=tree, files
> KF5AtticaConfig.cmake.in and CMakeLists.txt
>
>
> Best regards, Denis Kuplyakov.
>
> 2015-07-27 16:41 GMT+03:00 Vishesh Handa <me...@vh...>:
>
>> Sure. Makes sense. It needs to be done.
>>
>> Do you want to give a date by which you would like this done? I'm
>> putting it on my todo list.
>> Vishesh Handa
>>
>>
>> On Wed, Jul 22, 2015 at 6:52 PM, Денис Купляков <den...@gm...>
>> wrote:
>> > Hello Vishesh,
>> >
>> > My propose for now is:
>> > 1) applying my patch,
>> > 2) we are writing README.PACKAGERS to make situation according
>> > QT5_BUILD flag clear,
>> > 3) I don't think my patch needs any serious testing, it is a simple
>> > addition of plugin metainfo (also I should notice that Qt5 builded
>> > version on my setup passing more unittests than Qt4 version does)
>> > 4) announcing a new 2.(x+1) release with a single change: Qt5 support.
>> > I can make a post on planet KDE. Also some "release mail" on this list
>> > will be fine.
>> >
>> > What do you think? I need sometime for Soprano to live, cuz porting
>> > RDF support of Calligra to another library requires a big effort.
>> >
>> > Best regards, Denis Kuplyakov.
>> >
>> > 2015-07-18 13:34 GMT+03:00 Vishesh Handa <me...@vh...>:
>> >> Hey Денис
>> >>
>> >> On Wed, Jul 15, 2015 at 8:25 PM, Денис Купляков <den...@gm...>
>> wrote:
>> >>> What is a status of the project? Could we in Calligra be sure that at
>> >>> least this patch will get into the release and we will be able to
>> >>> access Soprano qt5 version in distros?
>> >>
>> >> The project hasn't seen any commits since Oct 2013, and even then it
>> >> was only getting updates required for Nepomuk. When I took over
>> >> Nepomuk, I guess I also took over Soprano.
>> >>
>> >> The Soprano code actually lives on the kde servers, so if you're a kde
>> >> developer you can just push the code there.
>> >>
>> >> Regarding making a new release, I'm not sure what the process would
>> >> be. Should I be releasing Soprano 3 or continuing 2.x? I'm no longer
>> >> using Soprano in any personal projects, so I don't even test it out.
>> >>
>> >> --
>> >> Vishesh Handa
>>
>
>