Running rpmlint within mock

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason L Tibbitts III wrote:
> OK, here's a first pass hack.  This could be better written in Python
> and could extract some bits from the mock configuration, but this does
> at least work.  It builds the package, installs rpmlint and all of the
> newly-built binary RPMs and (hopefully) their dependencies into the
> chroot.  It then runs rpmlint on the SRPM, the binary RPMs and the
> installed package names.  I have tested this against packages which
> show different warnings for each and it seems to actually work.
>
> You'll have to edit to taste, and try not to hurl as some of the
> quoting is nasty.
>
>  - J<
>
Note that using mockhelper is deprecated, since we've re-architected
so that mock becomes a chroot launcher for mock.py. Mockhelper will go
away in the next release (0.7).

Just so you know, I have a version of mock that takes a --rpmlint
command line option which will add rpmlint to the chroot transaction
set, install it in the chroot and then run rpmlint on the generated
SRPM and RPMs, putting the output in an rpmlint.log results file.  It
wasn't very intrusive and won't affect build systems unless they
specifically invoke it.

As an aside, I wouldn't mind looking at mock as a chroot builder for
things like the test project. It's mostly there, since it's main job
is to build a chroot and run rpmbuild within that chroot.  We should
discuss.

Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEukxNHyuj/+TTEp0RAgR2AKCOviuiwMw1apU/YXSXig7bzvmzggCeI+fB
qJ6PTlrYp5XRxGhMbrGWiLA=
=rQrE
-----END PGP SIGNATURE-----