kde November 2012

kde@lists.fedoraproject.org

17 participants
15 discussions

Packagers of plasmoids (Plasma applets): please run plasma-dataengine-depextractor in %build
by Kevin Kofler 09 Nov '12

09 Nov '12

Hi, since I just noticed that even the newly submitted kde-print-manager was missing this, here's a gentle reminder to all maintainers of Plasma applets: in your specfiles, at the beginning of the %build section, please add something like the following: if [ -x %{_bindir}/plasma-dataengine-depextractor ] ; then plasma-dataengine-depextractor plasmoid-package fi (The if check can be dropped once Fedora 16 reaches its end of life.) See: https://fedoraproject.org/wiki/Features/Plasma_PackageKit_Integration for why this is required. The syntax of the plasma-dataengine-depextractor tool is: plasma-dataengine-depextractor [path] [file] where: * "path" is the path to the source code of the plasmoid (relative to the current directory) – defaults to "." and * "file" is the file name or path (relative to "path", NOT to the current directory) of the .desktop file – defaults to "metadata.desktop" (If only one argument is specified, it will be interpreted as a "path", so if you want to specify only "file", you have to pass "." explicitly for the "path" argument.) If you have multiple applets, then multiple calls to plasma-dataengine-depextractor are needed. The only case where this is not required is if the .desktop file shipped by upstream already contains a: X-Plasma-RequiredDataEngines=… key (which may or may not be empty), but chances are it won't, because upstream refused to merge the Plasma PackageKit Integration into kdelibs 4 (they want it in KDE Frameworks 5 only). But thankfully, only a straightforward command is needed in the specfiles to autodetect the dependencies. Now, strictly speaking, it is also not technically required if either no data engines are used at all (as in some very simple plasmoids) or all data engines used are provided by the plasmoid package itself (as happens to be the case for kde-print-manager), but IMHO it is still a good idea to run the depextractor even in that case because a later updated version of the plasmoid may start requiring additional data engines. And before you ask why this is not done by the RPM auto-Requires script, this is because that script does not necessarily have access to the source code: Especially in the case of compiled (C++) plasmoids, the detection MUST be done from the source tree. So the auto-Requires script just always expects the depextractor to have been run, no matter what language the plasmoid was written in. Kevin Kofler

2 2

+1
by Peter G. 07 Nov '12

07 Nov '12

kde-4.9.3

1 0

KMail folder not appearing
by Timothy Murphy 06 Nov '12

06 Nov '12

I'm running KMail on my Fedora-17/KDE laptop, collecting email from an dovecot/IMAP server on a remote CentOS-6.3 machine that I control. I created a new KMail folder "MathProblems" by going to File=>New=>Add Folder on my laptop, and I verified that this created a folder ~/Mathdir/.MathProblems on the dovecot server (which stores email in ~/Mathdir), with the usual cur, new, tmp sub-folders. However, the files dovecot.index, dovecot.index.cache, etc, do not appear in the .MathProblems folder as they do in other similar folders, and the folder does not appear in KMail on my laptop. Is this a KMail or Dovecot bug? And is there any way of creating the missing files? Any advice or suggestions gratefully received.

1 0

kde failure after update on fedora 17
by Mark Gaudry 03 Nov '12

03 Nov '12

I maintained updates on my Fedora 17 system regularly. About 4 updates back most of my kde based programs stopped working. I kept adding updates with the hope that the problem would be solved. It has only gotten worse. I can no longer run apper or the updater from the notification icon. What have I done wrong or installed that might be causing this? I have installed multiple user interfaces and choose the one I use from the login screen listings. Could one of the others be conflicting somehow? If so which one is usually the worst culprit? I'll go in with one of the more reliable alternatives and remove the bad one(s). Any other ideas are also greatly appreciated.

2 2

Plasma Netbook or Active on Fedora ?
by linux guy 02 Nov '12

02 Nov '12

Is Plasma Netbook still around ? Is Plasma Active 3 ready for semi production use ? It can't be worse than Jelly Bean, can it ? Is there an easy way to install either of these on an existing Fedora install without wrecking it ? I'd really like to give one or both of them a try. Thanks

3 7

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde November 2012