https://bugzilla.redhat.com/show_bug.cgi?id=928584
--- Comment #7 from Rich Mattes <richmat...@gmail.com> --- Basically, the python and lisp compontents are the generated messages. They are required during runtime for any python or lisp program that needs the messages, though not every ROS program will need one or both of them. I think it would be possible to split them out into something like package-python-msgs and package-lisp-msgs, but I'm not convinced it's worth the effort. As far as /usr/share/common-lisp/ros goes, I'm not sure we can use that folder as per [1]. I think I may have to change the way that catkin is installing the lisp messages so that it lands in a packagename subfolder (or maybe we can just move the ros/ folder into common-lisp/source and have ros-release own it) You're right about requiring the runtime genpy and genlisp libraries: all the python getnpy messages import genpy. I'm not sure about lisp, and it looks like the c++ generated headers require headers from roscpp_core-devel. I'll update the Requires accordingly. I don't think egg-info needs to be generated; that guideline is only for when upstream does generate it, which isn't the case here. [1] http://fedoraproject.org/wiki/Packaging:Lisp#Install_location_and_hooking_into_the_common-lisp-controller -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=a3RBUGmnV2&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review
