Red Hat Bugzilla – Bug 439395
Explosive growth in abiword package
Last modified: 2008-03-29 13:27:53 EDT
The update to abiword 2.6 brings with it a substantial size growth as well as
new dependencies on the boost stack, sending the live image spiraling again over
the size of a CD.
The package should probably be split into the parts that are "required" and the
I _really_ want to prevent it to be split up. Ubuntu does this for example, and
ubuntu users _still_ believe we do not have OpenDocument support.
What we should do is investigate where the size changes comes from. If anything,
it should be smaller (except for the Boost dependency), as we removed lots of
old code in 2.6.0.
What is the actual size diff anyway (can't check atm)?
abiword grew by 22.45% (17682582->21653001)
But yes, boost is the biggest offender -- because in addition to that growth,
boost + all of its supporting stuff gets pulled in which costs us on the order
of 20-25 megs
Wow, didn't know we were the only user of boost :) The boost dependency is for
the AbiCollab only (at least for 2.6.x, for 2.7 it will most likely be required
I'd hate to make it optional, as we suspect it will become one of our most
important plugins. By making it optional, it will simply cease to exist for most
people (as they are not aware of additional packages; we see that in all other
distros all the time).
Yep, boost actually isn't that widely used. Partially because its dep chain is
somewhat ludicrous :-/
I can sympathize (somewhat) with your concern about people not knowing about it,
but given that it's *packaged in separate source tarballs*, it's already
somewhat off as far as the packaging guidelines are concerned.
And there's just no fat left for trimming on the live images and due to a major
version bump of abiword after the feature freeze, I've now gone from having
breathing room to being over on space usage.
About the separate source tarballs: it will all be a sane, single tarball again
for abi 2.7.x. We are moving away from our old arcane source tarball, so the 4
seperate packages are just a transition phase only thingy.
Otoh, I don't want to get you into trouble with your size issues. The only
solution I see now is making the abicollab plugin a seperate package. I'll do
this in an hour, unless you can come up with a more elegant solution :)
Sorry for the trouble.
Btw, other distro's split up boost in tons of packages. Isn't that the true
proper solution? We only use about 0.1% of boost, so it's a bit silly to have to
drag in 40MB of garbadge for that.
We could also fork boost, and include the tiny fraction of code we actually use,
but I'd rather not do that.
Hmm, it seems we are only depending on the boost threading library:
libboost_thread-mt.so.3 => /usr/lib/libboost_thread-mt.so.3 (0x0022c000)
For the rest, we only use boost's templates, which obviously only have a compile
Lemme try removing the boost threading with pthreads.
Other idea: I'll just link that libboost_thread lib statically. That will remove
all runtime boost deps
Fixed; I patched upstream as well as the package in rawhide to remove all
runtime dependencies on libboost
Reopen, something is still dragging boost in :X
[root@localhost ~]# rpm -Uhv abiword-2.6.0-3.fc9.i386.rpm
error: Failed dependencies:
libboost_thread-mt.so.3 is needed by abiword-2.6.0-3.fc9.i386