On Thu, Feb 22, 2007 at 10:08:07AM +0100, Richard Guenther wrote: > So, unfortunately a automated tool for reducing BuildRequires is hard > because it actually needs to check if building is still possible.
If it was only that it wouldn't be that hard because you could actually test in an automated way whether a build succeeds or not. But it is actually harder because it would be needed to check whether it builds _and_ and result is what you wanted to have. For example a package that can be built with or without a specific optional support library with just less functionality without this support library would always tend to remove this dependency thus losing the (eventually) wanted functionality. You could also check this automatically but then every packager would need to write automatic tests for all such functionalities that can be checked by the build system. Unfortunately doing so is likely to be more work than just managing the dependencies manually. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:[EMAIL PROTECTED] "Quidquid latine dictum sit, altum sonatur."
pgpHNYVVBDMVR.pgp
Description: PGP signature
