On Sat, 7 Jul 2001, Stefan van der Eijk wrote:
> The result of the "BR march" should be that no matter which package
> you're going to rebuild, if you install the BuildRequires, a (hopefully)
> good package is going to come out. It's all got todo with closing the
> gaps in the dependancies. How these gaps are going to be closed will
> need to be seen, probably each case will find it's own solution.
>
> Hmmm... let me upload todays result ;-)
>
> Stefan
Sorry, I am writing all replies to this subject all at once, so I missed
what this one was in reference to -- maybe the binary search algorithm?
Anyway this would be pointless, because the point of Requires is so that I
don't have to install 1000 rpms that I don't need. As I've said, I have
done this and it's not fun. What's more, the package still isn't
guaranteed to compile.
One thing that would help, as I've detailed earlier, is to normalize the
BuildRequires. Even still, sometimes I search on romfind.net when a
package complains of a depdency that doesn't seem to exist anywhere in
cooker. Then once I find what package it is, installing it will usually
fix any depdency problems. Finding the missing dependency is the key of
course. Brute force won't really help that.
--
Sincerely,
David Walluck
<[EMAIL PROTECTED]>
