On Sat, Aug 04, 2007 at 07:49:56PM +1000, Brendon Costa wrote: > The tarball of all source necessary to build EDoc++ is 25M and extracted > it is: 47M.
> EDoc++ stores in its source tree patches against GCC along with the GCC > original tarballs, and at build time will extract the gcc tarballs into > the build directory and apply the patches before building it. This means > the builddir can be quite large, but all files in it are "derived" from > the ones in the source directory and can be deleted between builds > without any re-percussions. > I am not sure where the 1G comes from, unless talking about the > duplicity across various mirrors. No, this is an estimate based on the actual usage of pool/main/g/gcc-4.1 on current Debian mirrors. (12 archs * 3 versions * n binary packages) Your note on the size of the edoc binary package would give a smaller total than 1G, but AFAICS it would still be a rather large, rather niche package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
