The code cannot be compiled while skipping baloo support, to allow it to run on a system without baloo installed The baloo part should be made possible to remove automatically by the config or by a DCMAKE flag Reproducible: Always Steps to Reproduce: 1. compile code Actual Results: ----------------------------------------------------------------------------- -- The following REQUIRED packages could NOT be located on your system. -- You must install these packages before continuing. ----------------------------------------------------------------------------- * Baloo Core Libraries <https://projects.kde.org/projects/kde/kdelibs/baloo> Desktop-wide semantic information support ----------------------------------------------------------------------------- CMake Error at /usr/share/apps/cmake/modules/MacroLogFeature.cmake:152 (MESSAGE): Exiting: Missing Requirements Call Stack (most recent call first): CMakeLists.txt:101 (macro_display_feature_log) -- Configuring incomplete, errors occurred! See also "/home/ash/system/gwenview/src/build/CMakeFiles/CMakeOutput.log". See also "/home/ash/system/gwenview/src/build/CMakeFiles/CMakeError.log". Expected Results: Able to compile without depending on baloo
Why? You do not complain that Gwenview needs the KDE libraries, which are much bigger than the baloo core library.
If you can provide the information requested in comment #1, please add it.
Gwenview uses KDElibs, Qt, Libjpeg etc for its most basic functionality : Open/save dialogs, Drawing the UI, Decoding picture files. Each of those is essential for a program which purpose is a picture viewer Gwenview uses Baloo to index or search for pictures based on semantic data. This is not in any way required for basic functionality, but only for the users who actually do use the semantic search features In many other cases the semantic search functionality can be a problem - in many possible scenarios which are not the standard case of a private personal computer. Just a few examples include : School or library computers where many students enter their private email etc all with the same OS user account, and do not expect the picture viewer to store any trace behind IT department computer being used to rescue a valuable picture from a hard drive in its 5 last minutes of life, and requiring any effort to minimize disk access Forensics lab computer which is not supposed to store any information of what it sees - not on the drive under investigation and not on its own drive Gwenview without semantic search features is a fully functional picture viewer/manager without semantic search features. There is need to be able to build a baloo-less version Gwenview can work without Baloo (i found a patch which another uses wrote, which just comments every refecence to Baloo functions. I compiled Baloo this way for my purposes), In contrast, it would not be possible to comment KDELibs functions and expect Gwenview to even work without them In many KDE and generalli Linux programs, it is a set norm that when program A can work with program/library B installed providing extra functionality, yet it may be fully functional without the features provided by B, then B is made an optional dependency of A What i am asking for in this bug report is, to let Gwenview function (less the semantic search) in a system in which Baloo is removed completly (which might be for purposes not related to Gwenview)
baloo fileindexing is already possible to be disabled (or packaging-wise, can be split between the support libraries and the indexer itself). making the gwenview baloo support optional at buildtime will only overly complicate matters further for little gain. (if not obvious, hence, I think it's ok to close this wontfix)
What use are the support libraries without the indexer ?
That's one current (and imo good) way of making the support modular
I mean this : What does Gwenview with the Baloo libs when the separate package of Baloo binaries is not installed ? Does it perform some sort of indexing or matching in its own right ?
nothing, no, respectively.
Then what is the sense in making it hard-depend on the presence of Baloo libraries like it is now ?
I too would like to see Baloo (and Akonadi) gone entirely rather soon than later from my system. It just makes no sense that those 2 are so deep connected to KDE while most users either don't use them or want them gone for good. Therefore I too kindly ask that Baloo should be at most optional.
I would also request the same. Can the version be changed to KDE 5?
https://cgit.kde.org/gwenview.git/commit/CMakeLists.txt?id=b8d6f9bfa5dbc53e6d2c58feea15ea1c3aa72a31