On 12/12/05, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > I wrote: > > > BUT, I disagree with the proposed method of obtaining this knowledge. > > As far as I can understand from the discussion, the method is to build > > all possible combinations of Current and Alphabetical chapter 6 from > > each other, and do some IPA. This will give us the knowledge whether > > those two build orders produce identical results. This knowledge is of > > zero value if the current build order misses some optional dependency. > > The only known true (but very expensive) method of determining package > > dependencies absolutely correctly without reading the whole source > > code is to run the whole build process under strace. > > > I take my words back. ICA does catch optional dependencies, but doesn't > provide an explicit list of them.
Right. I'm not saying ICA is a catch all for figuring out dependencies. However, it should help point out when the dependencies aren't correct or there are simply bugs in the build. If you know a better way to determine these, please share. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
