[yast-devel] Let's make minimal system smaller :) (41 MB)
Hi, Despite the fact that I don't want to be called "the one who reinvented the wheel", I'm still writing this mail :) I've found that some YaST packages have a huge amount of documentation but honestly, who reads such documentation and how often? Do we really want to have all this data in a minimal installation? This script checks all yast2* packages for size of their documentation and prints a sum at the end: SUM=0; for size in `du -s /usr/share/doc/packages/yast2* | \ sed 's/\([^ \t]*\).*/\1/'`; do \ echo $size; SUM=`expr 0${SUM} + ${size}`; done; \ echo; echo "Sum: ${SUM}" My system has about 58 MB of YaST documentation written in HTML. These are the biggest sinners: du -s /usr/share/doc/packages/yast2* | \ sort --general-numeric-sort | tail -n 10 646 /usr/share/doc/packages/yast2-repair 694 /usr/share/doc/packages/yast2-bootloader 737 /usr/share/doc/packages/yast2-nis-server 740 /usr/share/doc/packages/yast2-installation 1030 /usr/share/doc/packages/yast2-pkg-bindings 1073 /usr/share/doc/packages/yast2-network 1710 /usr/share/doc/packages/yast2-printer 2619 /usr/share/doc/packages/yast2 12372 /usr/share/doc/packages/yast2-storage 23191 /usr/share/doc/packages/yast2-core Sizes are in kilobytes. ------------------------------------------------------------------------ The best solution could be creating YaST "${name}-doc" packages containing only the documentation. They could be installed by default on a normal KDE/GNOME installation but not selected for a minimal installation. ------------------------------------------------------------------------ It seems to be quite easy change in an RPM .spec file... At least these packages should be split into ${name} and ${name}-doc: yast2-installation (0.7 MB), yast2-pkg-bindings (1 MB), yast2-network (1 MB), yast2-printer (1.7 MB), yast2 (2.6 MB), yast2-storage (12 MB), and yast2-core (22.6 MB) Only these can save up to 41 MB. What do you think of that? -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
* Lukas Ocilka <lukas.ocilka@suse.cz> [Jul 23. 2007 15:27]:
It seems to be quite easy change in an RPM .spec file...
At least these packages should be split into ${name} and ${name}-doc:
yast2-installation (0.7 MB), yast2-pkg-bindings (1 MB), yast2-network (1 MB), yast2-printer (1.7 MB), yast2 (2.6 MB), yast2-storage (12 MB), and yast2-core (22.6 MB)
Only these can save up to 41 MB. What do you think of that?
Fully agreed. Push Coolo to accept a mandatory request for 10.3 ;-) Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dne pondělí 23 červenec 2007 15:58 Lukas Ocilka napsal(a):
Klaus Kaempf wrote:
Fully agreed.
Push Coolo to accept a mandatory request for 10.3 ;-)
Here you can see the diff needed for yast2-installation.spec to build the yast2-installation-doc too (attached).
Are we really allowed to ship the package without the text of the license? OTOH, currently there are two copies of the license in the package, and (at least according to RPMlint) they can be replaced by a link to package containing licenses. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
Jiri Srain wrote:
Are we really allowed to ship the package without the text of the license?
OTOH, currently there are two copies of the license in the package, and (at least according to RPMlint) they can be replaced by a link to package containing licenses.
My patch didn't remove the license from the original yast2-installation :) The same (license) file is in both yast2-installation and yast2-installation-doc. L.
On Monday 23 July 2007 15:27, Lukas Ocilka wrote:
I've found that some YaST packages have a huge amount of documentation but honestly, who reads such documentation and how often? Do we really want to have all this data in a minimal installation?
I suggest to drop the autodocs completely. It takes considerable time to build them and just as much time to "make install" them, and they are little more than reformatted header files anyway. Most developers will look into the sources rather than bother with those generated HTML files anyway. The real documentation OTOH (the one that got written as doc, not just generated from some headers) we should keep IMHO. But that's very little compared to the huge amount of the generated autodocs. CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Lukas Ocilka wrote: [...]
------------------------------------------------------------------------ The best solution could be creating YaST "${name}-doc" packages containing only the documentation. They could be installed by default on a normal KDE/GNOME installation but not selected for a minimal installation. ------------------------------------------------------------------------
There already is "YaST Development" pattern (devel_yast-*.pat), I think that all yast2-*-doc packages should be part of that pattern (instead of KDE/GNOME)... Ladislav -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (5)
-
Jiri Srain -
Klaus Kaempf -
Ladislav Slezak -
Lukas Ocilka -
Stefan Hundhammer