surprised on space requirement

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

surprised on space requirement
by me on Friday 02/Jun/2006, @10:13

Managed to upgrade 3.5.2 -> 3.5.3, using packages from opensuse
repository (http://ftp-1.gwdg.de/pub/opensuse/repositories/KDE:).
Have to say I'm surprised that the upgrade increases KDE's space
usage by 150-200MB :).

This is on an old laptop with 20GB HDD; space is premium and
I allocated only 3GB for my root partition (tmp and var are
on the same partition). Before the upgrade, I had >300MB free
space. Now, I have about 150MB.

Too bad I can't downgrad to 3.5.2, the rpms has been removed
from suse's supplementary.

Related Links

·   Articles on KDE Official News
·   Also by me
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: surprised on space requirement
by me on Friday 02/Jun/2006, @10:30

I wonder what're the size taken by similar installed
packages? Mine takes about 690MB (25 packages). This
is on Suse 10.0.

cd /opt/kde3; du -shc *
=======================
59M bin
12K env
440K include
477M lib
156M share
8.0K shutdown
692M total

rpm -qa '*kde*' | sort
======================
kdeaddons3-konqueror-3.5.3-6.1
kdebase3-3.5.3-3.5
kdebase3-SuSE-10.0-21.3
kdebase3-kdm-3.5.3-3.5
kdebase3-ksysguardd-3.5.3-3.5
kdebase3-nsplugin-3.5.3-3.5
kdebase3-samba-3.5.3-3.5
kdebase3-session-3.5.3-3.5
kdegraphics3-3.5.3-6.2
kdegraphics3-extra-3.5.3-6.2
kdegraphics3-pdf-3.5.3-6.2
kdegraphics3-postscript-3.5.3-6.2
kdegraphics3-tex-3.5.3-6.2
kdelibs3-3.5.3-7.3
kdelibs3-arts-3.5.3-7.3
kdemultimedia3-3.5.3-14.3
kdemultimedia3-CD-3.5.3-14.3
kdemultimedia3-mixer-3.5.3-14.3
kdenetwork3-3.5.3-4.5
kdenetwork3-InstantMessenger-3.5.3-4.5
kdenetwork3-query-3.5.3-4.5
kdepim3-3.5.3-8.1
kdepim3-networkstatus-3.5.3-8.1
kdepim3-sync-3.5.3-8.1
kdeutils3-3.5.3-3.6

[ Reply To This | View ]

Re: surprised on space requirement
by me (again) on Friday 02/Jun/2006, @11:01

I found rpms for 3.5.2 from ftp.kde.org.

ftp://ftp.kde.org/pub/kde/stable/3.5.2/SuSE/ix86/10.0
ftp://ftp.kde.org/pub/kde/stable/3.5.3/SuSE/SUSE_Linux_10.0/i586

From a quick glance, each 3.5.3 package is at least twice
than its 3.5.2 counterpart. Examples:
arts-1.5.2-2 = 1MB --- vs --- arts-1.5.3-2.6 = 3.2MB
kdebase3-3.5.2-2 = 24.7MB --- vs --- kdebase3-3.5.3-3.5 = 52.2MB
kdepim3-3.5.2-2 = 12.9MB --- vs --- kdepim3-3.5.3-8.1 = 60.9 MB

I wouldn't expect a minor release to double space usage. Is
this merely a compilation problem, or indeed from KDE itself?

I attach two screenshots, one for suse rpms and the other for
Kubuntu drapper. I understand that comparing across distribution
is not the most appropriate way, but I hope this give some
indication.

suse.png
99KB (102129 bytes)

[ Reply To This | View ]

Re: surprised on space requirement
by me (again) on Friday 02/Jun/2006, @11:02

Here's the screenshot for kubuntu packages.

kubuntu.png
94KB (96843 bytes)

[ Reply To This | View ]

Re: surprised on space requirement
by Anonymous on Friday 02/Jun/2006, @23:22

> From a quick glance, each 3.5.3 package is at least twice than its 3.5.2 counterpart.

First revisions were built with debug information and not stripped. Later not anymore, reload.

[ Reply To This | View ]

Re: surprised on space requirement
by Anonymous on Friday 02/Jun/2006, @23:24

Update to stripped rpms once they are uploaded.

[ Reply To This | View ]

Re: surprised on space requirement
by me on Saturday 03/Jun/2006, @10:34

This did the trick.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Time for a make-it-cool branch?" -- Simon Hausmann
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.