[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE/kdelibs
From:       Leo Savernik <l.savernik () aon ! at>
Date:       2007-04-05 16:44:50
Message-ID: 200704051844.52005.l.savernik () aon ! at
[Download RAW message or body]

Am Mittwoch, 4. April 2007 schrieb Thiago Macieira:
> >> But the typical user will face the additional penalty of the above
> >> three libs. Your stats make the situation look better than it will be
> >> for the majority :-(
>
> Well, no, since libgcc_d isn't typical. In 10 years of Linux, this is the
> first time I've heard of it.
>
> Also, glib is an optional dependency for Qt. We in no way require it in
> KDE. (And you can imagine the flame war that would be caused by requiring
> it)

I know it's optional, yet e. g. Debian builds Qt with glib support by default. 
Other distributors probably do the same. This means, the typical user not 
compiling the Qt+KDE stack on his own will be penalised with additional 
glib+gobject (I don't know whether libgcc_d is part of glib) loading for 
*every* kde application. Well, actually, we (KDE) can't do anything about it.
>
> Next, the point wasn't to show that libkdecore links now to 16 or 19. It
> was to show that we link to 18 libraries less -- and heavy libraries at
> that.

This is really a great achievement. I'm also looking forward to the kdeui+kio 
merge.

mfg
	Leo

[prev in list] [next in list] [prev in thread] [next in thread]