[Bug 705043] Review Request: paco - a source code package organizer for Unix

[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=705043

Fabian Affolter <fabian@xxxxxxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fabian@xxxxxxxxxxxxxxxxx

--- Comment #2 from Fabian Affolter <fabian@xxxxxxxxxxxxxxxxx> 2011-06-04 12:19:35 EDT ---
Just some comment on your spec file:

- rpmlint output:

[fab@laptop021 SRPMS]$ rpmlint paco-2.0.9-1.fc14.src.rpm 
paco.src: E: description-line-too-long C After the installation of a source
package with "./configure && make && make install", one is usually left with
having no idea of what it was installed and where it all went, making it
difficult to uninstall the package in the future.
paco.src: E: description-line-too-long C When installing a package from
sources, paco wraps the "make install" command (or whatever command or group of
commands are needed to install the files into the system), and saves
installation information into a text database.
paco.src: E: description-line-too-long C Paco has many usage options for
removing packages, looking at package files, file counts, sorting, missing
files, etc. Run "paco -h" on the command line, or "man paco" for more
information.
paco.src:13: W: configure-without-libdir-spec
1 packages and 0 specfiles checked; 3 errors, 1 warnings.

[fab@laptop021 x86_64]$ rpmlint paco*
paco.x86_64: E: description-line-too-long C After the installation of a source
package with "./configure && make && make install", one is usually left with
having no idea of what it was installed and where it all went, making it
difficult to uninstall the package in the future.
paco.x86_64: E: description-line-too-long C When installing a package from
sources, paco wraps the "make install" command (or whatever command or group of
commands are needed to install the files into the system), and saves
installation information into a text database.
paco.x86_64: E: description-line-too-long C Paco has many usage options for
removing packages, looking at package files, file counts, sorting, missing
files, etc. Run "paco -h" on the command line, or "man paco" for more
information.
paco.x86_64: W: shared-lib-calls-exit /usr/lib64/libpaco-log.so.0.0.0
exit@xxxxxxxxxxx
paco.x86_64: E: incorrect-fsf-address /usr/share/doc/paco-2.0.9/COPYING
paco.x86_64: W: no-manual-page-for-binary ocap
2 packages and 0 specfiles checked; 4 errors, 2 warnings.

- Development .so files needs to go to a -devel subpackage
- ChangeLog file is missing in %doc

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


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