Ag. D. Hatzimanikas wrote these words on 08/03/07 14:28 CST: > Sorry I wasn't clear. I was asking about the tarball size. Should we > count it also into the build size?
No, we haven't been. However, there always seems to be some that think we should and some that think we shouldn't. The logic behind not counting the tarball size is this: The disk space used number is how much disk space a reader is required to have available to build the package after he has downloaded/acquired/whatever the tarball. You see, if one reader already has the tarball in a repo somewhere on disk and another reader does not and must download it, then the space required could be significantly different (large packages) if we counted the tarball. By not counting the tarball, disk space used is consistent whether you need to download the tarball or not. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 14:35:00 up 1 day, 14:26, 1 user, load average: 0.16, 0.12, 0.32 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
