While I'm not a SIG member, may I suggest that
a.) Nepomuk will be dropped in favor of Baloo and
b.) Post announcements via the usual channels ( http://fedoramagazine.org
Google+, Facebook, etc.) that an update will be released and explain that the
index will be recreated / converted and that this may take a while.
We did the same back in the day when Nepomuk 2.0 succeeded 1.x in the official
announcement, resulting in IIRC zero "Nepomuk got buggy and eats CPU"
On Monday 23 June 2014 11:11:41 Rex Dieter wrote:
Rex Dieter wrote:
> On 06/22/2014 07:20 PM, Markus Slopianka wrote:
>> Not sure why it seems to happen with every update but once again
>> kde-workspace 4.11.10 tries to install Nepomuk. ;-)
>> Is there anything we can do to help fix this?
> it's just that the nepomuk-free kde-workspace build from kde-unstable
> got superceded by a recent update:
> We have concrete plans to start work on brining kde-4.13.x to f20
> officially, but I guess we haven't decided on how best to deal with the
> nepomuk transition yet (ie, whether remove nepomuk-related deps from
> core kde packages or not).
OK, kde-sig members, please add your opinion this topic ^^.
I think I'm of a mind to removing optional nepomuk-related deps when
kde-4.13.x lands, since
* baloo migrates old nepomuk data
* nepomukserver no longer runs, so the related features don't really work
kde mailing list
New to KDE4? - get help from http://userbase.kde.org