-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason L Tibbitts III wrote:
Christian Iseli and I were discussing the possibility of
automatically
running rpmlint somehow. It seems that the end of the mock build
process is the ideal place for this. It has a chroot already set up
with the package's build requirements already installed. (Obviously
this doesn't include the runtime requirements, but generally there's
quite some overlap.) It also has easy access to the freshly built
binary and source RPMs.
How difficult would it be to, at the end of the build process, install
the freshly built package, install rpmlint, and run rpmlint on the
source and any binary RPMs that were built?
Sounds like a good idea.
Why do we need to install the just-generated binary RPMs in the
chroot? Can't we get the same info by just running rpmlint against the
binary and source RPMs?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org
iD8DBQFEt+abHyuj/+TTEp0RAvtPAJ4iHlPJFP2ofetHfwFGrSSKuv1wogCcDn2u
8Rv7tZiv3JZkXadh9+mK/Es=
=/0dA
-----END PGP SIGNATURE-----