https://bugs.kde.org/show_bug.cgi?id=374310
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1i5t5.dun...@cox.net
--- Comment #3 from Duncan <1i5t5.dun...@cox.net> ---
Here's the reviewboard discussion and patches that made appstream required.
https://git.reviewboard.kde.org/r/129697/
Third bullet-point in that list: "Drops PackageKit-Qt optional dependency, adds
a required AppstreamQt dependency instead."
You can read the discussion, but the decision was deliberate in that patch, and
none of the core devs reviewing it objected.
FWIW the Gentoo bug I opened on it, to either get appstreamqt in the gentoo/kde
overlay (where the kde-live ebuilds are) and ultimately the main tree, and
added as a (possibly patched to USE-flag optional) plasma-desktop dep, now for
the live build, later for releases, or get the dependency patched back out or
at least made optional.
https://bugs.gentoo.org/show_bug.cgi?id=604356
But Gentoo's general policy, and certainly the gentoo/kde general policy, is to
follow upstream where possible, tho the packagekit-qt dependency remained
optional (via packagekit USE flag) as it was upstream, and masked via
base-profile packagekit use-mask (as unready...) so unavailable unless users
deliberately unmasked it as well, so the option was deliberately difficult to
turn on.
But gentoo/kde wouldn't make the baloo dependency optional until upstream did,
so I was having to patch it out here on my own, as all that thing did here was
cause trouble.[1]
Which unfortunately looks like what I might be trying to do with this appstream
thing, too, at least temporarily, to get plasma-desktop building again. The
individual commit is of course easy enough to (effectively) revert, but how
many commits going forward will be based on that one, potentially ultimately
making patching it out unmaintainable in practice, is unknown. But it may be
the easiest short-term solution to get plasma-desktop-live building again,
until gentoo gets the appstream-qt package in-tree and initial deps worked out,
at least. Beyond that, and actually even that since I've not actually tried
the revert yet, to see what newer commits already depend on it, remains to be
seen.
Yea for freedomware, where we at least have the /option/ to do our own builds,
including out-of-upstream patches if found necessary. =:^)
---
[1] Baloo trouble: Build trouble due to weird symlink-related cmake issues
that I never resolved since it was easier just to run an earlier cmake version
and ultimately to patch out the baloo dep since I had no intention of using
baloo anyway, and as with various kde4 tech indexes, space trouble if baloo was
actually allowed to run because my /home's space budget doesn't include
gigabytes extra for otherwise unnecessary and of little use indexing files. At
least I'm 64-bit so baloo's known 32-bit index-file-size crashing issues didn't
affect me.
Hopefully this doesn't read too much like a rant. Baloo is officially optional
on the plasma desktop again now, after all, thanks to plasma's devs making it
so. But I was glad I was running freedomware and the option to patch it out was
there (and relatively easy thanks to both plasma and gentoo making it so), when
it wasn't officially optional. =:^) Credit where it's due! =:^)
Hopefully appstream will ultimately be officially optional again, as well. =:^)
Duncan
--
You are receiving this mail because:
You are watching all bug changes.
