On Friday 14 July 2006 16:11, Christian.Iseli(a)licr.org wrote:
AFAIU, rpmlint can catch more/other things when a package is
installed.
So the full thing seems to be:
1 rpmlint the src.rpm
2 rpmlint the <binary/noarch>.rpm
3 install the rpm and then run rpmlint again
Since mock builds a chroot anyway, Jason and I thought it might not cost
much more just to install the built packages and do an rpmlint then
This sounds like much more of a job of the Fedora Test Project software that
Will Woods is talking about. Then you could do more tests like testing for
conflicts, testing for scriptlet errors, testing for upgrade path / removal,
etc.. A much more appropriate place for it.
--
Jesse Keating RHCE (
geek.j2solutions.net)
Fedora Legacy Team (
www.fedoralegacy.org)
GPG Public Key (
geek.j2solutions.net/jkeating.j2solutions.pub