[Bug 467402] Review Request: mingw32-glib2 - MinGW Windows GLib2 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.


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


Tim Lauridsen <tim.lauridsen at googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|fedora-review?              |fedora-review+




--- Comment #12 from Tim Lauridsen <tim.lauridsen at googlemail.com>  2009-01-26 09:10:42 EDT ---
MUST:
* package is named according to the Package Naming Guidelines
    mingw32-*
* spec file name match base package
* package meet Packaging Guidelines 
* package is licensed with a Fedora approved license and meet the Licensing
Guidelines
* License field match the actual license.
* available license(s) file(s) is included in %doc.
* spec file is written in American English. 
* spec file is legible. 
* package compile on x86
* build dependencies is listed in BuildRequires
* available locales handled properly. (%find_lang macro)
* no shared libs
* package not relocatable
* package own all directories that it creates.
* no duplicate files in the %files listing. 
* Permissions on files must be set properly. (%defattr(...) line)
* %clean section present and contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT)
* package is consistently using macros
* package contain code, or permissable content
* no large doc
* %doc does not affect runtime
* no headers (native)
* no static libs
* available pkgconfig(.pc) files 'Requires: pkgconfig' 
* no *.so.* libs
* no -devel packages
* package dont contain .la libtool archives.
    no native ones
* not a GUI app.
* no files or directories already owned by other packages.
* %install begins with rm -rf %{buildroot} (or $RPM_BUILD_ROOT)
* filenames is valid UTF-8

APPROVED.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.