I don't recall any formal decision being made about including it by default. Do you remember otherwise? If a decision hadn't been made, I'd make a counter-proposal: * hide the default kcm by default (but keep installed, so callers to 'kcmshell4 baloofile' still works) * install baloo-kcmadv (by default, via deps or comps or whatever, don't care about implementation details), but *keep* the existing description, ie, "(Advanced)" to make it clear it is not the default one -- Rex ________________________________________ From: kde-bounces@xxxxxxxxxxxxxxxxxxxxxxx <kde-bounces@xxxxxxxxxxxxxxxxxxxxxxx> on behalf of Kevin Kofler <kevin.kofler@xxxxxxxxx> Sent: Thursday, January 15, 2015 9:15 AM To: kde@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: baloo-kcmadv in f20/kde-unstable repo Rex Dieter wrote: > It's an opt-in kind of thing, I think we chose not to install it by > default. It's not that we chose not to, it's just that nobody bothered to add the Requires. I still think that we should be shipping only baloo-kcmadv instead of the crippled default KCM, changing the description to remove the "(Advanced)". _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
