Trimming bzr package size

[Martin Pool]

2009/6/9 Brad Schick <schickb at gmail.com>:
> I am deploying bzr 1.15 on Ubuntu Linux systems and noticed that the PPA
> for bzr 1.15 is rather large for a command-line tools (currently just
> over 5MB). Somewhat ironically, I noticed this due to much slower repo
> clones after pushing bzr's .dep into a bzr repository. Looking into this
> a bit, I found that most of the bulk is in the docs:

Hi, thanks for reporting this, you're quite right that it is too big.

I filed <https://bugs.edge.launchpad.net/bzr/+bug/385074>


>
> /usr/share/doc/bzr$ du -h
>
> 288K    ./txt/developers
> 24K    ./txt/en/developer-guide
> 116K    ./txt/en/release-notes
> 4.0K    ./txt/en/mini-tutorial
> 28K    ./txt/en/tutorials
> 172K    ./txt/en/user-reference
> 212K    ./txt/en/user-guide
> 4.0K    ./txt/en/admin-guide
> 560K    ./txt/en
> 4.0K    ./txt/es/mini-tutorial
> 12K    ./txt/es/guia-usuario
> 16K    ./txt/es
> 876K    ./txt
> 1.4M    ./html/developers
> 88K    ./html/en/developer-guide
> 504K    ./html/en/release-notes

> - Many debian/ubuntu packages provide non-essential documentation in
> separate "-doc" packages. This might be a good idea for bzr. In
> particular the developer docs, but I'd actually prefer everythiny except
> man/info pages be extracted.

I agree.

> - Both of those large PNG images can be reduced by 50% or more by
> converting them to indexed (quantized) images. Currently they are 24bit
> RGBs. For example, I can't personally see any different after running
> "convert performance.png +dither -colors 32 performance_indexed.png".
> And the result is 537K smaller!
> - Other smaller PNGs don't convert so well perhaps due to lots of
> anti-aliasing. Although not as important, it seems like those could be
> simplified and indexed as well.

I think performance.png is now obsolete and could just be removed.

-- 
Martin <http://launchpad.net/~mbp/>