I've been working with Jeremy (and Nicolas) so we can finally get this over
with. This is a heads-up about the strigi-analyzers. The current situation
is as follows:
1) Nobody seems to have very strong opinions about whether to have the
analyzers with the apps or their own repo (among the
On 3 June 2012 18:39, Kevin Kofler kevin.kof...@chello.at wrote:
Hi,
for Kompare:
Friedrich W. H. Kossebau wrote:
repo name / display name: kompare / Kompare
description: Graphical File Differences Tool
project manager (user id on projects.kde.org needed): kkofler
OK
layout in
This is not the latest src, the issue has been fixed in revision 1299650.
On Jun 11, 2012 6:42 AM, Lindsay Mathieson lindsay.mathie...@gmail.com
wrote:
On Mon, 11 Jun 2012 07:17:27 AM you wrote:
Am Montag, 11. Juni 2012, 15:09:46 schrieb Lindsay Mathieson:
kdesrc-build, truck, latest src
I think the general way to do this is to write a strigi analyzer.
Strigi is a service running in the background indexing your files.
This information is stored in Nepomuk and that is where Dolphin gets
the information from. I guess that in theory the strigi analyzer could
fetch data from the
SVN commit 1299656 by doerner:
Make umbrello build fail gracefully if required libraries are not installed.
This is necessary when building the whole kdesdk module.
CCMAIL: kde-sdk-devel@kde.org
M +2 -1 CMakeLists.txt
--- trunk/KDE/kdesdk/umbrello/CMakeLists.txt #1299655:1299656
@@
Hi,
until we have finished the split and also release individual tarballs,
we have to support whole module builds. For splitting the root
CMakeLists.txt, we wanted to restrict the code in there to lines like
kdesdk_optional_add_subdirectory(umbrello)
without checking for any required packages
