[Bug 239546] Review Request: mdsplib - METAR Decoder Software Package Library

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: mdsplib - METAR Decoder Software Package Library


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239546





------- Additional Comments From lxtnow at gmail.com  2007-05-29 00:25 EST -------
Well,

OK - Mock : Built on FC6 en F-7 (i386 and x86_64)
OK - Package meets naming and packaging guidelines
OK - Spec file matches base package name.
OK - Spec has consistant macro usage.
OK - Meets Packaging Guidelines.
OK - License field in spec matches
OK - License is LGPL
OK - License match extras packaging policy licenses allowed
OK - License file is included in package
OK - Spec in American English
OK - Spec is legible.
OK - Sources SHOULD match upstream md5sum:
c529c07675431f50c517921db6fdd122  mdsplib-0.11.tar.gz
OK - Package has correct buildroot.
OK - extras BuildRequires not required for this package.
OK - %build and %install stages is correct and work.
OK - Package has %defattr and permissions on files is good.
OK - Package has a correct %clean section.
OK - Package is code or permissible content.
OK - Packages %doc files don't affect runtime.
OK - Package has no duplicate files in %files.
OK - Package doesn't own any directories other packages own.
OK - Changelog section is correct.

OK - Should function as described.
OK - Should package latest version

------------------------------------------------
Rpmlint output:
------------------------------------------------
OK - silent on both srpm and rpm.



-----------------------------
sub-package:
----------------------------

just a comment:
Why don't create directly the -devel package instead.
Does this package plan to contains more than headers files in future release ?

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.