Ken Moffat wrote these words on 07/29/05 21:25 CST: > The key is to have a reasonable idea of what each package contributes, > then keep rearranging the pieces until you're happy. There are a few > circular dependencies in the sense that foo improves bar, bar is > necessary for baz, and baz can improve the experience of foo.
You will find these are very rare. Most times, just using some forethought and knowledge of what your goals are, makes it easily possible to compile everything just once. Works for me, anyway. I can't think of one package I need to compile twice to get things the way I want. And I can assure you, I compile more BLFS and dependency packages than most folks will. -- 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] 21:34:00 up 118 days, 21:07, 2 users, load average: 0.00, 0.04, 0.26 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
