[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Why do X .debs take so much damn room to build? (was: Pentium Optimized)

On Thu, Jul 08, 1999 at 09:41:38PM -0400, Johnie Ingram wrote:
> "Thomas" == Thomas Ko <thomasko321m@gmx.at> writes:
> Thomas> Hi, Can you, "Martin Bialasinski"
> Thomas> <martin@internet-treff.uni-koeln.de>, tell me where you have
> Thomas> read that the x maintainers had 1.5 G of sources to compile or
> Thomas> binaries??? - I can't really believe this number.
> It was taking 1.5GB to hold the X dir after dpkg-buildpackage had done
> absolutely everything, on my box, at -- but this may be
> specific to i386 arch, or to my machine, or both.  :)

I'm pretty sure the #1 reason for this is policy 4.1, which mandates the
usage of "-g" as a CFLAG.  In hamm, slink, and earlier, X wasn't built with

By the time the process is done, you have the following situation:
1) post-compilation X source tree (loads of unstripped stuff)
2) debian/xtree, which contains the complete set of files installed by the
   X make process (loads of unstripped stuff)
3) the package build directories, which contain almost all the stuff from
   2), cp'ed...not mv'ed (stripped stuff)
4) the finished .debs sitting above the source tree (stripped, compressed

Even worse, i386 and m68k add libc5-compiled X libraries, which result in
smaller (but substantial) versions of 1-4 above.

Even with all this bloat and redundancy, in slink days you could build X in
about half the space it now requires.

Mind you, I'm not advocating the reversal of the -g policy.  Just trying to
explain why an X build takes so damn much space.

G. Branden Robinson              |   The key to being a Southern Baptist:
Debian GNU/Linux                 |   It ain't a sin if you don't get caught.
branden@ecn.purdue.edu           |   -- Anthony Davidson
cartoon.ecn.purdue.edu/~branden/ |

Attachment: pgpn7yeOL3NDj.pgp
Description: PGP signature

Reply to: