[Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter

[Sebastian Trueg]

Sebastian Kügler wrote:
> On Thursday 04 February 2010 16:16:34 Tom Albers wrote:
>> Op Thursday 4 February 2010 16:02 schreef u:
>>> On 02/04/2010 07:43 AM, Sebastian Trueg wrote:
>>>> Rex Dieter wrote:
>>>>> FYI,
>>>>> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter
>>>>>
>>>>> 1.  The requirements for kde-4.4/nepomuk have changed pretty late in
>>>>> the game (after all 4.4rc's).
>>>> No, they did not. I always said that Virtuoso 6 would be the dependency
>>>> for KDE 4.4.
>> You can not add a new dependency for KDE 4.4 the day before the release
>> without testing. I consider it a new feature which is not allowed since
>> ages. for KDE 4.5 I've planned to add it to the release schedule
>> explicitly to make it even more clear. It is too late in the cycle for 4.4
>> to change this dependency. Really. Some packagers can not add a new
>> dependency to their repository in one day and have prepared the KDE 4.4
>> packaging based on the 4.4 release candidates we have given them. Please
>> don't do this.
>>
>>> Fact is that we're in a bad situation of now requiring something that's
>>> been untested and it's data is incompatible with what was tested.
>> +1
>> Unacceptable imho.
> 
> What will happen is that distros will ship Virtuoso 6 anyway, because they don't want 

That has been the plan for a long time now and the major distros already
knew that. Like I said: Debian, SuSE and Mandriva have been in contact
with OpenLink for a long time to clean up the code tree (licence-wise)
and figure out the best packaging scheme.

> to introduce V5, and then have to convert users' data again (first time from the 
> sesame2) backend. I don't know in how far V6 is different from V5, other than the 
> dataformat, but we might consider recommending V6 anyway, because it has a clearer 
> road forward.
> 
> It's a bit unfortunate that there was a bug in V6.0 that prevented us from testing 
> with it, that seems fixed in 6.1?
> 
> I'd also be interested in more (dis)advantages of V6 over V5, and how different V5 
> and 6 actually are from a "what can break KDE?"-point of view. Sebastian, can you 
> give more details?