mak added a comment.
In https://phabricator.kde.org/D3923#73574, @anthonyfieroni wrote:
> In https://phabricator.kde.org/D3923#73375, @mak wrote:
>
> > In any case, knowing the distro might be useful to check whether their
packaging makes sense ;-)
>
>
> KaOS don't have
anthonyfieroni added a comment.
In https://phabricator.kde.org/D3923#73375, @mak wrote:
> In any case, knowing the distro might be useful to check whether their
packaging makes sense ;-)
KaOS don't have appstream nor appstreamQt nor Discover (it's a fairly normal
when first two
hein added a comment.
I'm in principle OK with this patch, but also don't mind the change apol
requested if it makes him happier since it's his code.
In this context I'd like to mention that I was slightly surprised/miffed that
the original change went into Kicker during my vacation
mak added a comment.
@davidedmundson What do you mean with big dependency chain? libappstream and
libappstreamQt depend in total on only libxml2, libyaml, GLib and Qt5Core which
pretty much any distro, especially with Plasma on it, should already have
anyway.
Didn't you use Neon? Or was
