KDE Telepathy has an unreleased dependency

Martin Klapetek martin.klapetek at gmail.com
Wed Feb 25 17:39:46 GMT 2015

On Wed, Feb 25, 2015 at 6:33 PM, David Faure <faure at kde.org> wrote:

> On Wednesday 25 February 2015 15:38:19 Aleix Pol wrote:
> > At the moment KPeople is an optional dependency, there's still the
> > possibility to use it without KPeople.
> I guess you mean s/KPeople/Baloo/g here.

No this was actually KPeople being optional dep of KTp, but the truth is
all the code is actually only tested with KPeople as that's pretty much what
we're aiming for in the past couple years (but KPeople went through many
many changes, it started as Nepomuk thing, then akonadi, now it's
so we never wanted to hard-depend on it). Now we've optimized everything
for KPeople usage so imho it makes only sense to not discard it now and
in fact make it finally a hard-dependency of KDE Telepathy.

> The problem is: Baloo depends on a few frameworks,
> and now we would have KPeople depending on Baloo.
> So it wouldn't be possible to build all of frameworks together, one would
> need
> to interject Baloo in the middle of it, in order to be able to build "with
> all
> options" i.e. with this optional dependency.
> The reason "it's optional so it doesn't matter" means you might as well
> delete
> the code, since it becomes impractical to build it anyway.
> More seriously I would suggest moving the plugin to Baloo maybe, if it
> makes
> sense for it to depend on KPeople, or moving it in workspace maybe (but
> then
> it's not available in other workspaces). Or to this new "product" (set of
> modules) that I think we should have to host drkonqi, kio-extras etc., i.e.
> the set of runtime deps common to workspace and applications. This issue
> keeps
> popping up.
> If you want a short term solution, I'd say the plugin should stay in
> playground somewhere.
> I don't like the optional dependency thing because it will still show up in
> dependency diagrams, making a mess with baloo being in the middle of
> frameworks while it was decided that it's not.

As I said it's not even being used right now, so imho would be fine if it
removed/disabled altogether.

Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20150225/b13d3dc3/attachment.htm>

More information about the kde-core-devel mailing list