[Bug 184331] Review Request: K-3D - 3D modeling and rendering system

[bugzilla at redhat.com]

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: K-3D - 3D modeling and rendering system


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184331





------- Additional Comments From denis at poolshark.org  2006-08-01 12:02 EST -------
SPEC: http://www.poolshark.org/src/k3d.spec
SRPM: http://www.poolshark.org/src/k3d-0.5.15.0-2.src.rpm

- I cleaned up the %files section a bit, as you requested. The package does
indeed have both libraries in /usr/lib and /usr/lib/k3d (those are plugins).

- For the undefined-non-weak-symbol warnings. I believe this is intentional. See
here: http://www.redhat.com/archives/fedora-extras-list/2006-July/msg00569.html
Essentially you are getting the warnings because the package dependencies are
not installed. As for the weak linking, I believe it is intentional to allow k3d
libs to link to either libGL.so from Xorg or from Nv***a.

- For the devel vs non-devel. Part of the package can be considered a devel
package, but I dont think it does what a traditional devel package would do. The
reasons has to do with what K-3D does: it's merely a modeler, the first step
before calling the main rendering engine (e.g. aqsis, which I'll try to package
next), and that step involves using the devel-type files. So the devel files are
required by the main package. This is explicitely mentioned in the project page
at http://www.k-3d.org/wiki/GettingStarted , as well as in comment #1 above. I
brought up the issue on a fedora mailing list a while ago, but I can't seem to
track it down in the archives. I remember the consensus was that it made little
sense to split a package if both parts require each other. OTOH I can't say I
have a strong opinion on the matter...

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