Hello, On šeštadienis 01 Gegužė 2010 02:16:59 Regis Boudin wrote: > I'm the maintainer of Tellico, and I tried to build it against the coming > KDE4.4.2 from experimental. I noticed the split of the package into > libraries, which is great. However, I also noticed that they pretty much > all make the application linking to them depend on kdepim-runtime. > > This pretty much seems to defeat the purpose of splitting the package, > since tellico ends up depending on kdepim-runtime, which in turn pulls > akonadi-server (and mysql-server-core as well). This was not a purpose of splitting but rather a side effect. Our *-runtime stuff is still monolithic and it is complicated to split them due to lack of support for such configuration upstream and unpredictable effects on the end applications. > Tellico is linked to libkcal and libkabc for really non-core features, > therefore it would be really nice if you could remove the dependency on > kdepim- runtime in the shlibs files, so the users don't end up pulling all > the kdepim infrastructure for an optional feature. kdepim is heading towards akonadi being mandatory. You need akonadi to access calendar (kcal) and addressbook (kabc) as of KDE SC 4.4. So that kdepim- runtime injection is rather logical. What is more, could you be more specific which non-core features you have in mind here? It is possible to nitpick kdepim-runtime injection on the symbol level but we need to get those things right from the first try. -- Modestas Vainius <modestas@vainius.eu>
Attachment:
signature.asc
Description: This is a digitally signed message part.