[Bug 471231] Review Request: WebCalendar - Single/multi-user web-based calendar application

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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=471231





--- Comment #9 from David Nalley <david@xxxxxxx>  2009-07-09 23:12:38 EDT ---
Package review for webcalendar.

Package Review Guidelines

MUST: rpmlint must be run on every package. The output should be posted in the
review.
[ke4qqq@nalleyt61 SPECS]$ rpmlint ./WebCalendar.spec 
0 packages and 1 specfiles checked; 0 errors, 0 warnings.
[ke4qqq@nalleyt61 SPECS]$ rpmlint ../SRPMS/WebCalendar-1.2.0-6.fc11.src.rpm 
1 packages and 0 specfiles checked; 0 errors, 0 warnings.
[ke4qqq@nalleyt61 SPECS]$ rpmlint
../RPMS/noarch/WebCalendar-1.2.0-6.fc11.noarch.rpm 
WebCalendar.noarch: W: dangling-symlink
/usr/share/WebCalendar/includes/classes/phpmailer/class.smtp.php
/usr/share/php/PHPMailer/class.smtp.php
WebCalendar.noarch: W: non-standard-gid /etc/WebCalendar/settings.php apache
WebCalendar.noarch: E: non-readable /etc/WebCalendar/settings.php 0660
WebCalendar.noarch: W: dangling-symlink
/usr/share/WebCalendar/includes/classes/hKit/hkit.class.php
/usr/share/php/hkit/hkit.class.php
WebCalendar.noarch: W: non-standard-gid /etc/WebCalendar apache
WebCalendar.noarch: E: non-standard-dir-perm /etc/WebCalendar 0775
WebCalendar.noarch: W: dangling-symlink
/usr/share/WebCalendar/includes/classes/phpmailer/class.phpmailer.php
/usr/share/php/PHPMailer/class.phpmailer.php
1 packages and 0 specfiles checked; 2 errors, 5 warnings.

OK: The package must be named according to the Package Naming Guidelines .
OK: The spec file name must match the base package %{name}, in the format
%{name}.spec unless your package has an exemption. 
OK: The package must meet the Packaging Guidelines .
OK: The package must be licensed with a Fedora approved license and meet the
Licensing Guidelines .

GPLv2 throughout source code and in GPL.html

OK: The License field in the package spec  file must match the actual license.
OK: 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

OK: The spec file must be written in American English.
OK: The spec file for the package MUST be legible. 
OK: 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 
[ke4qqq@nalleyt61 SOURCES]$ md5sum WebCalendar-1.2.0.tar.gz*
520bd108e9e4d2a14425d2b5b8cc2e1e  WebCalendar-1.2.0.tar.gz
520bd108e9e4d2a14425d2b5b8cc2e1e  WebCalendar-1.2.0.tar.gz.1

OK: The package MUST successfully compile and build into binary rpms on at
least one primary architecture. 
NA: 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. 
OK: 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.
NA: The spec file MUST handle locales properly. This is done by using the
%find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.
OK: 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. 
NA: 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. 
OK: 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. 
OK: A Fedora package must not list a file more than once in the spec file's
%files listings. 
OK: Permissions on files must be set properly. Executables should be set with
executable permissions, for example. Every %files section must include a
%defattr(...) line. 
OK: Each package must have a %clean section, which contains rm -rf %{buildroot}
(or $RPM_BUILD_ROOT). 
OK: Each package must consistently use macros. 
OK: The package must contain code, or permissable content. 


QUESTION: 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). 
This is up to your discretion - I personally don't think it constitutes a
separate subpackage - however upstream did package it separately. 
You may also want to consider moving this to %doc and symlinking
datadir/name/docs to that directory. 


OK: 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. 

NA: Header files must be in a -devel package. 
NA: Static libraries must be in a -static package. 
NA: Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig' (for
directory ownership and usability). 
NA: If a package contains library files with a suffix (e.g. libfoo.so.1.1),
then library files that end in .so (without suffix) must go in a -devel
package. 
NA: In the vast majority of cases, devel packages must require the base package
using a fully versioned dependency: Requires: %{name} = %{version}-%{release} 
NA: Packages must NOT contain any .la libtool archives, these must be removed
in the spec if they are built.
NA: 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. 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. 
OK: 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. 
OK: At the beginning of %install, each package MUST run rm -rf %{buildroot} (or
$RPM_BUILD_ROOT). 
OK: All filenames in rpm packages must be valid UTF-8. 


This is starting to look pretty close - I am going to reply to one other item
in this review shortly.

-- 
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.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]