Could kdecore depend on kjs?

[Lubos Lunak]

On Friday 16 of March 2007, Thiago Macieira wrote:
> Stephan Kulow wrote:
> >Hmm, the cache is hopefully cold only once. How shall this sum up? But
> > yes, libkjs will have to be loaded into memory for the first KDE app
> > too - while so far it stayed on disc before khtml was loaded.
>
> I think this dependency is far too specific:
> - only some applications will make use of it
> - moreover, only on some languages
> - what's more, only if certain strings are displayed
>
> That's why I think a loadable plugin is better.

 I admit this may look like I'm trying to be nasty, but does this mean we 
should also try to make e.g. libidn a loadable dependency? I think the list 
above actually matches its case nicely as well.

 It'd be actually interesting if somebody compiled KDE without some of the 
less often needed dependencies and checked how big difference it makes. Using 
ldd on some binaries lists rather interesting things:

ldd kreadconfig  (KDE4)
        libutil.so.1 - WTH is this?
        libbz2.so.1 - huh?
        libidn.so.11 - see above
        libXtst.so.6 - WTF?????
        libX* - bloody tiny X libs
        librt.so.1 - WTH is this?

ldd kwrite (KDE4)
        libkdesu.so.5 - which KDE apps actually do need this?
        libfam.so.0 
        libacl.so.1
        libattr.so.1 - and these 3?
        libQtSql.so.4 - SQL in KWrite?

-- 
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak at suse.cz , l.lunak at kde.org
Lihovarska 1060/12   tel: +420 284 028 972
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http//www.suse.cz