SRPM's and determining spec file

[Alan Milligan]

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

Hi,

Not sure if this is the right place to discuss the behaviour of RPM, but
I'm sure somebody can correct me!

I have a requirement to determine the spec file from a SRPM so that my
rpmbuild can be guaranteed to be passed a valid file.

I'd hoped to just find in the BASENAMES, however, it seems to be
filtered out when using rpm -q.

So then I thought I'd just use the RPM2 perl module.  This indeed works,
excepting that it fails constantly due to bad signatures etc in packages:

error reading package at
/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi/RPM2.pm line 85.

To my mind (i) rpm -q --qf"%{BASENAMES}" should not filter the .spec
file; and (ii) the RPM2 perl module should return as much of the header
as it can construct, with undefs etc in bad fields.  Even throwing an
exception or returning an error code would at least put the decision in
user space.

I am happy to provide a patch for either if someone would indicate a
preference.

Cheers, Alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBYv5DCfroLk4EZpkRAnyxAKDOUdnARVP5u+lpVI3uF7L98H2iiACfaeP3
WjZHpzRxqlW8pLxS0MtqQW8=
=5ltK
-----END PGP SIGNATURE-----