Re: Packaging review guidelines clarification

[Mike McGrath <mmcgrath fedoraproject org>]

> I think a failure to build in mock is a blocker, unless the reason is
> either a deficiency in mock (in which case there should be a reference
> to the bugzilla ticket for the issue raised on mock), or a dependency
> not available in Core or Extras yet (which can easily be worked around
> by adding a local repo containing the missing dependency to the
> reviewer's mock configuration).
>
> Remember that the build system uses mock, so if it won't build in mock,
> it won't get built for Extras at all.
>
> Paul.

I'm all for it, should we move 'should build on mock' to 'must build
on mock' in the wiki?

         -Mike