From Fedora Project Wiki

Line 5: Line 5:
'''Author:''' [[TomCallaway|  Tom 'spot' Callaway]] <BR>
'''Author:''' [[TomCallaway|  Tom 'spot' Callaway]] <BR>
'''Revision:''' 0.27<BR>
'''Revision:''' 0.28<BR>
'''Initial Draft:''' Monday Jun 27, 2005<BR>
'''Initial Draft:''' Monday Jun 27, 2005<BR>
'''Last Revised:''' Friday Nov 30, 2007<BR>
'''Last Revised:''' Tuesday Dec 16, 2008<BR>
== Package Review Process ==
== Package Review Process ==

Revision as of 23:16, 16 December 2008

Package Review Guidelines

This is a set of guidelines for Package Reviews. Note that a complete list of things to check for would be impossible, but every attempt has been made to make this document as comprehensive as possible. Reviewers and contributors (packagers) should use their best judgement whenever items are unclear, and if in doubt, ask on the fedora-packaging list .

Author: Tom 'spot' Callaway
Revision: 0.28
Initial Draft: Monday Jun 27, 2005
Last Revised: Tuesday Dec 16, 2008

Package Review Process

Contributors and reviewers should follow the Package Review Process.

Things To Check On Review

There are many many things to check for a review. This list is provided to assist new reviewers in identifying areas that they should look for, but is by no means complete. Reviewers should use their own good judgement when reviewing packages. The items listed fall into two categories: SHOULD and MUST.

MUST Items
Items marked as MUST are things that the package (or reviewer) MUST do. If a package fails a MUST item, that is considered a blocker. No package with blockers can be approved on a review. Those items must be fixed before approval can be given.
  • MUST: rpmlint must be run on every package. The output should be posted in the review.[1]
  • MUST: The package must be named according to the Package Naming Guidelines .
  • MUST: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption. [2] .
  • MUST: The package must meet the Packaging Guidelines .
  • MUST: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines .
  • MUST: The License field in the package spec file must match the actual license. [3]
  • MUST: If (and only if) the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package must be included in %doc.[4]
  • MUST: The spec file must be written in American English. [5]
  • MUST: The spec file for the package MUST be legible. [6]
  • MUST: The sources used to build the package must match the upstream source, as provided in the spec URL. Reviewers should use md5sum for this task. If no upstream URL can be specified for this package, please see the Source URL Guidelines for how to deal with this.
  • MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. [7]
  • MUST: If the package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. Each architecture listed in ExcludeArch MUST have a bug filed in bugzilla, describing the reason that the package does not compile/build/work on that architecture. The bug number MUST be placed in a comment, next to the corresponding ExcludeArch line. [8]
  • MUST: All build dependencies must be listed in BuildRequires, except for any that are listed in the exceptions section of the Packaging Guidelines ; inclusion of those as BuildRequires is optional. Apply common sense.
  • MUST: The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.[9]
  • MUST: Every binary RPM package (or subpackage) which stores shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in %post and %postun. [10]
  • MUST: If the package is designed to be relocatable, the packager must state this fact in the request for review, along with the rationalization for relocation of that specific package. Without this, use of Prefix: /usr is considered a blocker.
  • MUST: A package must own all directories that it creates. If it does not create a directory that it uses, then it should require a package which does create that directory. Refer to the Guidelines for examples.
  • MUST: A package must not contain any duplicate files in the %files listing.
  • MUST: Permissions on files must be set properly. Executables should be set with executable permissions, for example. Every %files section must include a %defattr(...) line.
  • MUST: Each package must have a %clean section, which contains rm -rf %{buildroot} ( or $RPM_BUILD_ROOT ).
  • MUST: Each package must consistently use macros, as described in the macros section of Packaging Guidelines .
  • MUST: The package must contain code, or permissable content. This is described in detail in the code vs. content section of Packaging Guidelines .
  • MUST: Large documentation files should go in a -doc subpackage. (The definition of large is left up to the packager's best judgement, but is not restricted to size. Large can refer to either size or quantity)
  • MUST: If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present.
  • MUST: Header files must be in a -devel package.
  • MUST: Static libraries must be in a -static package.
  • MUST: Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig' (for directory ownership and usability).
  • MUST: If a package contains library files with a suffix (e.g., then library files that end in .so (without suffix) must go in a -devel package.
  • MUST: In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name} = %{version}-%{release}
  • MUST: Packages must NOT contain any .la libtool archives, these should be removed in the spec.
  • MUST: Packages containing GUI applications must include a %{name}.desktop file, and that file must be properly installed with desktop-file-install in the %install section. This is described in detail in the desktop files section of the Packaging Guidelines . If you feel that your packaged GUI application does not need a .desktop file, you must put a comment in the spec file with your explanation.
  • MUST: Packages must not own files or directories already owned by other packages. The rule of thumb here is that the first package to be installed should own the files or directories that other packages may rely upon. This means, for example, that no package in Fedora should ever share ownership with any of the files or directories owned by the filesystem or man package. If you feel that you have a good reason to own a file or directory that another package owns, then please present that at package review time.
  • MUST: At the beginning of %install, each package MUST run rm -rf %{buildroot} ( or $RPM_BUILD_ROOT ). See Prepping BuildRoot For %install for details.
  • MUST: All filenames in rpm packages must be valid UTF-8.

Items marked as SHOULD are things that the package (or reviewer) SHOULD do, but is not required to do.
  • SHOULD: If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it.
  • SHOULD: The description and summary sections in the package spec file should contain translations for supported Non-English languages, if available.
  • SHOULD: The reviewer should test that the package builds in mock. See MockTricks for details on how to do this.
  • SHOULD: The package should compile and build into binary rpms on all supported architectures.
  • SHOULD: The reviewer should test that the package functions as described. A package should not segfault instead of running, for example.
  • SHOULD: If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity.
  • SHOULD: Usually, subpackages other than devel should require the base package using a fully versioned dependency.
  • SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and this is usually for development purposes, so should be placed in a -devel pkg. A reasonable exception is that the main pkg itself is a devel tool not installed in a user runtime, e.g. gcc or gdb.
  • SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the file instead of the file itself. Please see File Dependencies in the Guidelines for further information.

References to the Fedora Packaging Guidelines