Kontact build dependencies

kde pim

Adding KDE PIM to KDE neon I wondered if it really was as complex to build as it felt.  So I mapped them in Graphviz, and yep, it really is complex to build.  I’m quite amazed at the coders who work on this stuff, it’s an impressive beast.

Facebooktwittergoogle_pluslinkedinby feather

10 Replies to “Kontact build dependencies”

    1. Agreed. This kind of complexity and mad interdependency is probably the root cause of the constant problems of anything KDE-PIM. I wonder if anybody is still using it.

      Sadly, I feel that KDE in general is leaning towards building complex architectures for their own sake – every time I tried some quick hack to KDE applications (okteta, gwenview) it took a big effort even just to locate who actually did stuff through the myriad of layers of abstraction, and trying to compile the damn things was a dependency hell.

    2. I am afraid I must agree. And although I have deep sympathy for the developers and the ideas behind the project, after weeks of trying to make it work for me I have had to decide that it is just too complicated to be reliable. Moreover, for an average user (and no developer) such as me it is too time consuming to set up whilst there are some fundamental flaws (bugs?) which are frustrating. I had to switch back to Thunderbird incl. Lightning.

  1. So will PIM be ported to Neon? Some applications like KMail can already be found in Discover wonder if/when the whole Kontact suite will be. Love Kontact, by far the best PIM solution for Linux available. Thanks for your efforts!

  2. Come-on guys. A little bit of inducement here !

    Kontact is certainly not perfect but it’s packed of nice features and unmatched in the qt world. Recent kf5 refactors show a nice gain in performances and kontact team seems to have a roadmap.

    I use it since a long time, don’t intend to change, and I’m sure a lot of people are in the same spirit.

    Now if jonathan is dedicating time to include it into neon, it means on short terms, user friendly and regular upgrades, and easier compilation for dev.

    Thanks neon !

  3. Just wondering… did you filter it with tred? While not giving a picture as accurate as the complete graph, I have has some success using it to represent dependencies in a comprehensible way.
    Plus, transitivity is more or less a given for those dependencies, unless the ordering i important.

  4. LOL! If this is dependency hell, what is a Linux distro then?

    Graph ‘only’ the package deps of a base Linux install, you will see it’s by far the bigger knot. 🙂

    Or ever looked on the package deps of a bigger Java Project? You would get a graph with hundreds of nodes and thousands of edges…

Leave a Reply

Your email address will not be published.

Spam-proofing. What is next? a, b, ...?