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=639615 Ryan Rix <ry@xxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(mfojtik@xxxxxxxxx | |m) --- Comment #3 from Ryan Rix <ry@xxxxxxxx> 2010-10-12 21:08:02 EDT --- General Musts: + MUST: rpmlint must be run on every package. The output should be posted in the review. + 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. +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. +MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. [7] -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: 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: Packages must NOT bundle copies of system libraries.[11] 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. [12] +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. [13] +MUST: A Fedora package must not list a file more than once in the spec file's %files listings. (Notable exception: license texts in specific situations)[14] +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. [15] +MUST: Each package must consistently use macros. [16] +MUST: The package must contain code, or permissable content. [17] +MUST: Large documentation files must 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). [18] +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. [18] +MUST: All filenames in rpm packages must be valid UTF-8. [24] Ruby specific Packaging guidelines: +- Requires: ruby(api) = 1.8 +- BuildRequires: ruby +- Packages that contain Ruby Gems must be called rubygem-%{gemname} where gemname is the name from the Gem's specification. +- The Source of the package must be the full URL to the released Gem archive; the version of the package must be the Gem's version +-The package must have a Requires and a BuildRequires on rubygems +-The package must provide rubygem(%{gemname}) where gemname is the name from the Gem's specification. For every dependency on a Gem named gemdep, the package must contain a Requires on rubygem(%{gemdep}) with the same version constraints as the Gem +-The %prep and %build sections of the specfile should be empty. +-The Gem must be installed into %{gemdir} defined as %global gemdir %(ruby -rubygems -e 'puts Gem::dir' 2>/dev/null) +-The install should be performed with the command gem install --local --install-dir %{buildroot}%{gemdir} --force %{SOURCE0} +-Architecture-specific content must not be installed into %{gemdir} +-If the Gem only contains pure Ruby code, it must be marked as BuildArch: noarch. If the Gem contains binary content (e.g., for a database driver), it must be marked as architecture specific, and all architecture specific content must be moved from the %{gemdir} to the [#ruby_sitearch %{ruby_sitearch} directory] during %install .... So, after all of that, here's what I'm left with: !MUST: The sources used to build the package must match the upstream source, as provided in the spec URL. Please fix the URL, it's missing a / :) Source does match though. A few personal annoyances: I'm not sure that having LICENSE only in -docs is acceptable under guidelines. Please move it from %files docs to a %docs section in each package which rubygem-rvm.spec creates. Other than those two issues, this package is more or less a good example of how to package ruby gems :) Once those two issues are taken care of, we're good to go! -- 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. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review