williams(a)redhat.com said:
Getting the rpmlint output is easy enough. Doing anything more than
that
sounds like something out of the scope of mock.
Agreed.
Ah, we're talking automated test suite here.
Yup.
That's not mock.
Ok.
I applaud your desire to automate this stuff, but I don't think
that mock is
the right place for it. Mock is strictly a tool for managing a chroot and
building SRPMs in those chroots. Anything else just introduces the potential
for breaking builds and then Jeremy and Dan start sending me nasty emails :).
:)
That being said, I think it would be fairly straightforward to run
rpmlint on
the generated RPMs and on the SRPM and stash the output somewhere that's
easily accessible.
Yes, that'd be neat.
At that point you're talking about writing an analysis
tool to classify the output of a mock build.
Yes. I'd like to add that to plague, or as a standalone thing that is called
by plague after mock succeeds.
Christian