[Base] Proposal for buildrequires cleanup janitorial initiative

[Bruno Wolff III]

On Fri, Dec 13, 2013 at 17:25:49 -0800,
   Adam Williamson <awilliam at redhat.com> wrote:
>
>That's still not really enough; that metadata doesn't express anything
>*close* to all the possible capabilities of a package. Not saying this
>isn't a good idea, just that it should involve careful manual double
>checking of compose logs and the like.

Another possible problem is that if package A build requires packages 
B and C and today package B requires C, then this would likely result 
in the build requires for C being dropped. Then if later B no longer 
requires C, this will result in problems. If they are obvious then 
it won't be that big of a deal. But if the build succeeds and the package 
just doesn't work correctly there may be confusion as to why it stopped 
working.