Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Title: Szalai Kálmán
Hi!

It seems we ship makefile.mk
in
libreoffice/basis3.3/share/template/layout

That is not necessary.

KAMI

2011-01-21 17:26 keltezéssel, Michael Meeks írta:
Hi guys,

	So - I re-ran the analysis on RC4 which is here:

	http://users.freedesktop.org/~michael/sizes3.ods (2.2Mb)

	Apart from a minor cockup (leaving tons of themes in there - when we
only really want tango + hicontrast) - the next major source of bloat is
code, and the umpteen duplicated Wizard / templates.

	Hopefully we'll fix this in 3.3.1 - bringing us down to ~200Mb.

	Hopefully the binfilter write redux will yield some nice code size
shrinkage in due course, and we can nail the Wizard duplication in
master, which (if we can get it done) should bring us down to a ~160Mb
install for 3.4

	Of course, help dunging out the sillies that still lurk in there - eg.
'soffice.exe' and 'soffice.bin', bundled testtool, and so on much
appreciated.

	Work on shrinking the bloat is much appreciated [!] and best focused on
the wizards / templates.

	HTH,

		Michael.


--
KAMI911Best regards,

Kálmán „KAMI” Szalai | 神 | kami911 [at] gmail [dot] com


My favorite projects:

OxygenOffice Professional - office suite - for everybody | Magyarul - In Hungarian

Blog | Support 

Follow me, if you can

Attachment: signature.asc
Description: OpenPGP digital signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.