[Bug 474787] Review Requrest: stxxl - C++ STL drop-in replacement for extremely large datasets

bugzilla at redhat.com bugzilla at redhat.com
Fri Dec 5 15:10:19 UTC 2008


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





--- Comment #3 from D Haley <mycae at yahoo.com>  2008-12-05 10:10:18 EDT ---

SPEC URL: http://dhd.selfip.com/427e/stxxl-2.spec
SRPM URL: http://dhd.selfip.com/427e/stxxl-1.2.1-2.fc9.src.rpm

Changelog

* Sat Dec 06 2008 <mycae(a!t)yahoo.com> 1.2.1-2
- Removed latex build & buildrequires
- Patched makefiles to provide shared instead of static libs
- made doxygen log to file, due to excessively verbose output

Rpmlint:
SRPM:empty
SPEC:empty
RPM:
$ rpmlint -iv RPMS/i386/stxxl-1.2.1-2.fc9.i386.rpm 
stxxl.i386: I: checking
stxxl.i386: W: devel-file-in-non-devel-package /usr/lib/libstxxl-0.so
A development file (usually source code) is located in a non-devel
package. If you want to include source code in your package, be sure to
create a development package.

Now this is causing problems, If i put the link in the devel package it says it
must be part of the package proper and emits an error. If I put it in the main,
as I have done now, it emits this warning. The libstxxl-0.so is simply a
symlink to libstxxl.so.0. Running ldconfig -n during %install instead of
hand-cranking the symlink makes no difference, as the net result is the same.
It simply makes the symlink using the soname of the so. This soname is the same
value that I have set in the build patch (patch0).

Koji scratch: 
http://koji.fedoraproject.org/koji/taskinfo?taskID=981419
All succeeded.

Issues:
I don't build the user manual. This however can be grabbed from their sf page
by users, so unless someone knows the solution off the top of their head to the
latex problem, I will probably leave it.

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




More information about the package-review mailing list