Inconsistent usage of RPM macros leads to packaging bugs: * Package "player" includes directories included in package "player-examples". * Sometimes you write %{name}, sometimes you spell it out: player Use %{name} consistently. * The following two are redundant: %dir %{_libdir}/player %{_libdir}/%{name} The former one includes *only* the directory entry without its contents. The latter includes the directory and its contents recursively. (%name expands to "player"). In this case, drop the %dir line. * In main package add: %exclude %{_libdir}/%{name}/examples/ because this tree is included in the sub-package player-examples. * In package player-examples (and whenever including directories, make it more readable with a slash at the end. Instead of: | %files examples | %defattr(-,root,root,-) | %{_libdir}/player/examples Prefer: | %files examples | %defattr(-,root,root,-) | %{_libdir}/player/examples/ * Clean up the installed trees. Delete unused static libs, Makefiles, and C/C++ source files. * You do | Requires: python >= 2.5 while the Python ABI requirement is automatic: python(abi) = 2.5 * Who approved the -static sub-package? What is the rationale? It ought to be explained in a comment in the spec file.
Thanks for the comments. Will consider them for the next update. The static libs are used because especially in robotics and university applications you want to be able to build a static version to deploy it on a robot (possibly running a very specific Linux version where it could be a pain to install player) or sending a static build to a fellow researcher possibly using a different version. It just saves you hassle in certain situations so it is good to have the static lib around and have the possibility. That was discussed during the review. If you mean the example source files: they are included on purpose because that's the whole point of the examples, get an easy start on developing with Player, not on actually just using it. Basically Player is a development platform, not a "get it and drive your robot with it" kind of software.
Well, static archives won't work as plugins (as they cannot be dlopened), so including them in the examples is useless. And to include example Makefile.libtool files which do -rpath /tmp is bad taste.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
It seems you're not interested in fixing packaging issues. Closing WONTFIX.