Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: HippoDraw - Interactive and Python scriptable data analysis application https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208034 ------- Additional Comments From mtasaka@xxxxxxxxxxxxxxxxxxx 2007-03-12 14:26 EST ------- Well, before checking -2 package: (In reply to comment #31) > > To answer your question, HippoDraw can be built with any of the three numeric > packages for Python. The numarray package has been most commonly used up to > now so configre script enables it by default. The macros you see in the snipet > of code are defined in config.h. Perhaps config.h should be installed in > /usr/include/HippoDraw/ as part of the -devel package? Well, my question is that * at a build stage of HippoDraw, one of the three headers are "include"d in num_util.h, for example, Numeric/arrayobject.h * When I want to use num_util.h for other applications, the header file included in num_util.h may differ from above, for example, numarray/arrayobject.h Does this cause no problem? > > Question for you: The -devel package installs /usr/lib/libhippo.so and > /usr/lib/libhippoqt.so, Yes, this is needed for linkage. i.e. if you want to allow linkage against libhippo.so from other applications, this symlink is needed. > but the main package already does that. Umm? main package has /usr/lib/libhippo.so.0 (needed for ldconfig) or /usr/lib/libhippo.so.0.0.0 (this is the real file of the library), however these files cannot be used for linkage (i.e. -lhippo) > Should they be removed from the -devel package since > it requires the main package? Normally -devel package should require main package (or -libs package if there exists) and for linkage /usr/lib/libhippo.so is needed in -devel package. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review