John Gnew wrote these words on 03/15/05 16:46 CST: > I have redone the install and now have a number 109 MB which is still > smaller that the old of 146 MB.
Don't sweat it. The last time (or time before last) I updated ImageMagick I added a bunch of new optional dependencies. I had to make sure the depends I added would link and build correctly, so it caused ImageMagick to build modules for everything it finds. I usually try to build all, or most, of the optional dependencies with a package to ensure everything builds as expected. This causes some packages, especially ImageMagick, to use additional disk space building, and installing, the additional modules. Additionally, I run the test suite for the package, which in some cases adds lots of disk space. The whole point in the exercise is to put a number so folks will know approximately how much disk space they will *have* to have available to build and install the package. That's why you add the sources in. You can't delete the sources until you've installed the package. Therefore, at the point of maximum disk usage, is the number we want to put down in the book. I hope this makes sense. > I have also noticed that the bug 1066 has been assigned to Igor. Guess I > did not do things in the correct order. Again, don't sweat it. It is good practice however to check BZ and look for the package. That way, 2 guys won't be trying to do the same thing at the same time. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 17:13:01 up 13 days, 3:17, 3 users, load average: 0.00, 0.00, 0.00 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
