Bug 111976 - package kdeartwork icon themes separately
package kdeartwork icon themes separately
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kdeartwork (Show other bugs)
1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-11 22:12 EST by Keunwoo Lee
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-12-15 11:36:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Keunwoo Lee 2003-12-11 22:12:35 EST
The kdeartwork package bundles together several "look and feel" 
customizations (like kwin styles) and icon styles.  The icon styles 
account for the lion's share of kdeartwork's disk usage: in my 
installation of Fedora Core 1, 
 
  du -c /usr/share/icons/{Locolor,Technical,ikons,kdeclassic,slick} 
 
gives a total of over 22MB (even though though du -c --apparent-size 
gives only 6.5MB: icon themes are composed of the large number of 
very small files, which on ext2/ext3 occupy a full disk block 
regardless of their size). 
 
I want to use kdeartwork for the kwin styles and utilities, but 
would rather not pay 22+MB on my hard drive for a bunch of icon 
themes that I will never use.  This problem is going to get worse 
with KDE 3.2: judging by the beta, 3.2 will add another icon theme 
("kids"; apparent size 4MB, disk size almost 7MB) and move more kwin 
styles from kdecore to kdeartwork. 
 
It would not be necessary to package each icon theme separately, but 
if the icon themes as a whole could collectively be packaged as e.g. 
kdeartwork-icons, then it would be better.  Thanks.
Comment 1 Ngo Than 2003-12-15 11:36:07 EST
it should be fixed kdeartwork-3_1_94-0_2. thanks

Note You need to log in before you can comment on or make changes to this bug.