-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 8 Jul 2001, David Walluck wrote:
[finding BuildRequires lines for source packages]
>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.
The method I proposed would find the missing dependency, because it
would try *all* the packages. Every single one. It would be rather
slow, and it would grind your hard disk rather a lot, but it would find
the necessary set of packages in the end.
Of course doing this by hand is not fun. That's why it's best to
automate it. Even if the algorithm used is rather stupid compared to a
human (who can usually make intelligent guesses about what's needed), it
is a lot less work to just leave it running for a few hours and come
back to look at the results.
- --
Ed Avis <[EMAIL PROTECTED]>
Finger for PGP key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7SDoMIMp73jhGogoRAnNUAJ9SMKoNUlOD8CR22K2GtmP5/pgmWACeMu5j
g8l3uyioXlW/0qXHLniMlSk=
=CM9J
-----END PGP SIGNATURE-----
