Try using rpmlint, which should catch most of the common issues with rpm packages. See: http://people.mandrakesoft.com/~flepied/projects/rpmlint/
Look chaps, I know I'm the newcomer here and all that, but try to see it my way for a while.
I joined this list because I've written a package. I've been using it for years to do my own backups - so I know it works. I'd like to enter into the spirit of the open-source thing by giving it away free.
I'm a little bit mystified by the submission procedure. And the more I read the submission thread the more mystified I get. While I understand the need for QA, and can understand why packages ought to be PGP signed I really would appreciate a few hints about the way I should go.
For example, do I need to have pre and post install scripts? My little package contains a C source, a man page, a makefile and a spec file. Do I need to add other things to get through QA or is that enough?
Would somebody who knows how this works mind pointing me in the right direction? Thanks.
-- Robert Billing, Tanglewood, 01344-772849 64, Pinehill Road, rbilling@tnglwood.demon.co.uk Crowthorne, http://www.tnglwood.demon.co.uk/ Berks, RG45 7JR
-- fedora-devel-list mailing list fedora-devel-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-devel-list