docs make bzr package too big
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
John Ferlito |
Bug Description
Brad Schick <email address hidden> writes:
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:
/usr/share/doc/bzr$ du -h
288K ./txt/developers
24K ./txt/en/
116K ./txt/en/
4.0K ./txt/en/
28K ./txt/en/tutorials
172K ./txt/en/
212K ./txt/en/user-guide
4.0K ./txt/en/
560K ./txt/en
4.0K ./txt/es/
12K ./txt/es/
16K ./txt/es
876K ./txt
1.4M ./html/developers
88K ./html/
504K ./html/
16K ./html/
1.2M ./html/
84K ./html/en/tutorials
336K ./html/
276K ./html/
516K ./html/
2.7M ./html/en
16K ./html/
16K ./html/es
4.0M ./html
5.0M .
In particular, there are two 24 bit PNG images that add up to 1.3MB alone.
700K ./html/
644K ./html/
A few ideas:
- 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.
- 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_
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.
-Brad
Related branches
- John A Meinel: Approve
- Robert Collins (community): Approve
- Diff: 159 lines
2009/6/9 Brad Schick <email address hidden>:
> 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>
> developer- guide release- notes mini-tutorial user-reference admin-guide mini-tutorial guia-usuario en/developer- guide en/release- notes
> /usr/share/doc/bzr$ du -h
>
> 288K ./txt/developers
> 24K ./txt/en/
> 116K ./txt/en/
> 4.0K ./txt/en/
> 28K ./txt/en/tutorials
> 172K ./txt/en/
> 212K ./txt/en/user-guide
> 4.0K ./txt/en/
> 560K ./txt/en
> 4.0K ./txt/es/
> 12K ./txt/es/
> 16K ./txt/es
> 876K ./txt
> 1.4M ./html/developers
> 88K ./html/
> 504K ./html/
> - 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 indexed. png".
> 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_
> 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.
-- launchpad. net/~mbp/>
Martin <http://