[Clipart] Announcing Inkscape 0.40 Release
Christian Fredrik Kalager Schaller
uraeus at linuxrising.org
Wed Dec 1 04:49:05 PST 2004
Pango usage outside GTK+ might be limited, but glib is used by a LOT of
different stuff. So if gtk is the only thing you have installed on your
system using it then your system is something of an abnormality, and you
can't expect packagers to cater to abnormal systems. Since urpmi will
update all those deps for you anyway I have problems seeing why you have
an issue in the first place anyway.
> But I do NOT understand why GTK is linked dynamically against
> libglib and pango. Virtually nothing else besides GTK uses those
> libraries, so there's no good reason for the dynamic linking:
> root at vestibule ~/download :) # rpm -q --whatrequires libpango1.0
> root at vestibule ~/download :) # rpm -q --whatrequires libglib2.0
> root at vestibule ~/download :) # rpm -q --whatrequires libgtk+-x11-2.0_0
> root at vestibule ~/download :) #
> Not only is GTK quite pointlessly dynamically linked against libglib
> and pango, but it *itself* is subdivided into two packages, for
> absolutely no good reason.
> This is why I only have time to upgrade stuff at home, and at work
> I'm still using Gnome 1.4 -- at work, I can't justify the time to
> chase down a hillion jillion dependencies. I shouldn't have to do
> it at home either. Nobody should. Hard drive sizes being what they
> are, it no longer makes sense to save a couple of measley megabytes
> by inflicting superfluous pain on the user. Inkscape is an
> application I use with some frequency: as such, it's welcome to
> a few megabytes of drive space.
> One can only imagine the trouble I'd have put myself through if I'd
> downloaded the non-statically-linked version of Inkscape. <<shudder>>
> The take-home message is this: Static linking is GOOD, and the world
> needs more of it.
More information about the clipart