Mock going forward

[Chris Weyl]

On 8/16/06, Clark Williams <williams at redhat.com> wrote:
> Keeping in line with our razor-blade focus for mock ("we just build
> packages in chroots"), I actually don't think there's much more to do
> for 1.0. Once we are comfortable with the functional and security
> aspects of the 0.7 mock, I'd call it cooked. Assuming of course no one
> comes up with a killer feature that is :).

A while ago and on a different list, tibbs proposed adding one last
bit to the buildcycle:

* installing rpmlint into the buildroot
* installing the built packages into the buildroot
* running rpmlint against the installed packages and providing the
rpmlint reports in results/

The idea here is to seamlessly give rpmlint reports on installed
packages (there's a difference than on binaries, apparently) without
having the builder/reviewer needlessly clutter up their host.  Mock
wouldn't have anything to do with the results once rpmlint is run;
they'd just be another bit of information for the reviewers/packagers
to use.

My memory is a bit foggy on what happened to this, but is this
something we could think about doing for mock, either 0.7 or 1.0?
IMHO, something like this would be a great time saver, as it's
something that's fairly routine.

                          -Chris

-- 
Chris Weyl
Ex astris, scientia