Spec URL: http://rmattes.fedorapeople.org/rospackages/actionlib/actionlib.spec SRPM URL: http://rmattes.fedorapeople.org/rospackages/actionlib/actionlib-1.8.7-1.20130605git3827384.fc19.src.rpm Description: The actionlib package provides a standardized interface for interfacing with preemptible tasks. Examples of this include moving the base to a target location, performing a laser scan and returning the resulting point cloud, detecting the handle of a door, etc. Fedora Account System Username: rmattes rpmlint: $ rpmlint actionlib.spec ../../RPMS/x86_64/actionlib-* actionlib.x86_64: W: spelling-error Summary(en_US) pre -> per, ore, pee actionlib.x86_64: W: spelling-error Summary(en_US) emptible -> contemptible actionlib.x86_64: W: spelling-error %description -l en_US preemptible -> preemptive actionlib.x86_64: E: invalid-soname /usr/lib64/libactionlib.so libactionlib.so actionlib.x86_64: W: no-documentation actionlib-devel.x86_64: W: no-documentation 3 packages and 1 specfiles checked; 1 errors, 5 warnings.
Should this package be called ros-actionlib? I would find it easier if ROS packages (especially core packages) had a common prefix.
(In reply to Tim Niemueller from comment #1) > Should this package be called ros-actionlib? I would find it easier if ROS > packages (especially core packages) had a common prefix. I think so.
I don't think it's necessary. I've been using a virtual provides for ros-%{name} with the other packages (e.g. catkin). I think it's might be better to leave it as actionlib and use the virtual provides for ros-actionlib to be consistent.