Example inconsistency: kdelibs-4.13[semantic-desktop] builds "old" nepomuk library (and requies soprano, SDO deps) dolphin-4.13 understands 'semantic-desktop' as baloo, yet requires kdelibs[semantic-desktop?] (builds and seems to work fine without so dep bug likely) Seems like clear separation of "old nepomuk" and "baloo" is necessary. Now we have just "semantic-desktop". How to fix this and similar issues? Some options: 1. Keep 'semantic-desktop' USE flag & semantics + deprecate nepomuk completely where/if possible (to the point of removing ebuilds) 2. Introduce 'nepomuk' USE flag to handle "old" nepomuk library USE deps 3. Introduce 'baloo' USE flag to handle new desktop search library USE deps 4. Some mix of above Ideas?
5. Obviously.. drop semantic-desktop since 4.13 and feature baloo by default. (there is recent discussion on kde dev ml about 'button to disable baloo at runtime', currently it's just achievable by excluding home dir from index apparently). I know we can privide hard-switch like we did for nepomuk, but whether it's worth it it's different story.
baloo is still semantic-desktop, just in a different incarnation. The dolphin dep sounds like a bug, and I bet there's more like it. We can't remove nepomuk because kde-workspace still requires it, and I'm strongly against making baloo unconditional - there's just no reason to do it, and as we saw with nepomuk even if there is an off button a lot of people get upset. If the concern is baloo-only users pulling in virtuoso etc., we could rename kdelibs[semantic-desktop] -> kdelibs[nepomuk] and adjust the USE dependency throughout the tree.
(In reply to Michael Palimaka (kensington) from comment #2) > baloo is still semantic-desktop, just in a different incarnation. The > dolphin dep sounds like a bug, and I bet there's more like it. ++ - use flag name is fine. > We can't remove nepomuk because kde-workspace still requires it, and I'm > strongly against making baloo unconditional - there's just no reason to do > it, and as we saw with nepomuk even if there is an off button a lot of > people get upset. ++ > If the concern is baloo-only users pulling in virtuoso etc., we could rename > kdelibs[semantic-desktop] -> kdelibs[nepomuk] and adjust the USE dependency > throughout the tree. I am not sure if this is realy needed. We should refactor the consumers of kde-base/kdelibs[semantic-desktop] first (pull in nepomuk related pkgs).
(In reply to Johannes Huber from comment #3) > > If the concern is baloo-only users pulling in virtuoso etc., we could rename > > kdelibs[semantic-desktop] -> kdelibs[nepomuk] and adjust the USE dependency > > throughout the tree. > > I am not sure if this is realy needed. We should refactor the consumers of > kde-base/kdelibs[semantic-desktop] first (pull in nepomuk related pkgs). kdelibs conditionally builds libnepomuk depending on soprano and sdo, I think some consumers make use of that.
<johu> vHanda: whats the plan for kde-workspace on getting rid of nepomuk? <vHanda> it's gone for plasma next / KF5 <vHanda> kde-workspace is frozen in KDE4, so I'm not going to be touching <johu> whats the disadvantages to hard disable it in downstream on KDE SC 4.11 <vHanda> it doesn't make much of a difference <vHanda> as long as nepomuk is disabled, then the workspace parts of it won't use it. <vHanda> Actually, I think the only workspace part is the runner and one data engine. <johu> so the runner will work without nepomuk? <vHanda> yes, it just won't find files/emails. <vHanda> If you are on 4.13, then it will find stuff via baloo
I sorry for sticking my nose in here, but if baloo is now the new semantic-desktop as indicated via equery depends baloo kde-base/dolphin-4.13.0 (semantic-desktop ? >=kde-base/baloo-4.13.0:4[aqua=]) kde-base/gwenview-4.13.0 (semantic-desktop ? >=kde-base/baloo-4.13.0:4[aqua=]) then can all those semantic-desktop soprano / nepomuk ones be changed to something else so that we would be able to dump nepomuk/soprano and keep baloo? # equery depends nepomuk * These packages depend on nepomuk: kde-base/kdebase-runtime-meta-4.13.0 (semantic-desktop ? >=kde-base/nepomuk-4.13.0:4[aqua=]) kde-base/systemsettings-4.11.8 (semantic-desktop ? >=kde-base/nepomuk-4.11.8:4[aqua=]) # equery depends soprano * These packages depend on soprano: app-office/akonadi-server-1.12.1-r1 (soprano ? dev-libs/soprano[-qt4,qt5]) (soprano ? dev-libs/soprano) kde-base/kactivities-4.13.0 (dev-libs/soprano) kde-base/kdelibs-4.13.0 (semantic-desktop ? >=dev-libs/soprano-2.9.0[dbus,raptor,redland]) kde-base/kget-4.13.0 (semantic-desktop ? dev-libs/soprano) kde-base/lokalize-4.13.0 (semantic-desktop ? >=dev-libs/soprano-2.9.0) kde-base/nepomuk-4.13.0 (>=dev-libs/soprano-2.9.0[dbus,raptor,redland,virtuoso]) kde-base/nepomuk-core-4.13.0 (>=dev-libs/soprano-2.9.3[dbus,raptor,redland,virtuoso]) kde-base/nepomuk-widgets-4.13.0 (>=dev-libs/soprano-2.9.0) kde-base/plasma-workspace-4.11.8 (semantic-desktop ? dev-libs/soprano) kde-base/pykde4-4.13.0 (semantic-desktop ? >=dev-libs/soprano-2.9.0)
However it's done on USE flag level, I'll drop soprano related USE deps on akonadi-server from: kde-base/akonadiconsole-4.13 and above kde-base/kdepimlibs-4.13 and above kde-base/kdepim-runtime-4.13 and above kde-base/kdepim-common-libs-4.13 and above Rationale: zero nepomuk support in those anymore.
(In reply to Maciej Mrozowski from comment #7) > However it's done on USE flag level, I'll drop soprano related USE deps on > akonadi-server from: > > kde-base/akonadiconsole-4.13 and above > kde-base/kdepimlibs-4.13 and above > kde-base/kdepim-runtime-4.13 and above > kde-base/kdepim-common-libs-4.13 and above Done by johu.
Again, sorry for butting in again. In kde-meta-4.13.0.ebuild there is this: semantic-desktop? ( $(add_kdebase_dep kdepim-meta "" 4.4.11.1) ) Technically that seems no longer correct, as not having semantec-deskop does not prevent one from using kdepim does it? After accidentally removing it with depclean I reinstalled it and works as it did before. I use kdepim, use what baloo has to offer, and thank you for allowing me to dump nepomuk and friends.
So, if I want to use 4.13 without nepomuk/soprano/virtuoso, I have to 1.) Remove the semantic-desktop use flag for the ebuilds that pull in nepomuk whit this flag enabled, e.g. kdebase-workspace, kdebase-runtime-meta ... 2.) Enable the semantic-desktop use flag for the ebuild that pull in baloo with this flag enabled, e.g. dolphin Did I understand this correctly? A bit confusing, but ok;)
(In reply to Andreas Hermann from comment #10) > So, if I want to use 4.13 without nepomuk/soprano/virtuoso, I have to That's correct. This is why we have this discussion.
Is this all done now?
Guess it's done then.
