For anyone running a kde-plasma5 desktop who wonders what it takes to
kill it in 5 as USE=-semantic-desktop did in kde4...
I don't have a full kde5 desktop installed, but of what I have, only two
packages depend on baloo: kde-plasma/plasma-desktop and kde-plasma/plasma-
workspace.
I've been able to patch out the (source) deps, and instead of patching
the ebuilds themselves, I've placed those patches in the appropriate
/etc/portage/patches/kde-plasma/plasma-[desktop|workspace]/ locations so
the ebuilds apply them automatically, and either package.provided the
baloo package itself to fake the dep for the ebuilds (works, but
package.provided is deprecated), or created a fake baloo in my overlay
that installs no files (what I'm actually doing now).
That eliminates the actual baloo installation alone with the couple of
other packages that only it pulled in on my system.
Here's the enhancement bug I filled asking if the gentoo/kde project is
interested, with the two source patches attached.
https://bugs.gentoo.org/show_bug.cgi?id=578664
If /you/ as a gentoo/kde /user/ are interested, the two sources patches
are there. While you're there, commenting on the bug that you too would
like baloo to be optional, and mentioning anything else kde5-based on
your system that pulls in baloo, that likely also needs patched, would be
useful.
And of course don't forget to CC yourself on the bug if you want to
follow how it turns out.
Thanks.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
kill it in 5 as USE=-semantic-desktop did in kde4...
I don't have a full kde5 desktop installed, but of what I have, only two
packages depend on baloo: kde-plasma/plasma-desktop and kde-plasma/plasma-
workspace.
I've been able to patch out the (source) deps, and instead of patching
the ebuilds themselves, I've placed those patches in the appropriate
/etc/portage/patches/kde-plasma/plasma-[desktop|workspace]/ locations so
the ebuilds apply them automatically, and either package.provided the
baloo package itself to fake the dep for the ebuilds (works, but
package.provided is deprecated), or created a fake baloo in my overlay
that installs no files (what I'm actually doing now).
That eliminates the actual baloo installation alone with the couple of
other packages that only it pulled in on my system.
Here's the enhancement bug I filled asking if the gentoo/kde project is
interested, with the two source patches attached.
https://bugs.gentoo.org/show_bug.cgi?id=578664
If /you/ as a gentoo/kde /user/ are interested, the two sources patches
are there. While you're there, commenting on the bug that you too would
like baloo to be optional, and mentioning anything else kde5-based on
your system that pulls in baloo, that likely also needs patched, would be
useful.
And of course don't forget to CC yourself on the bug if you want to
follow how it turns out.
Thanks.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman