| rcl-yaml-param-parser |
3.1.2-1 |
Parse a YAML parameter file and populate the C data structure. |
meta-ros2-galactic |
| re2c |
2.0.3 |
Tool for writing very fast and very flexible scanners |
openembedded-core |
| rebar |
2.6.4-gitX |
rebar is an Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases. |
meta-erlang |
| rebar3 |
3.13.3 |
Erlang build tool that makes it easy to compile and test Erlang applications and releases. http://www.rebar3.org |
meta-erlang |
| rebar3 |
3.16.1 |
Erlang build tool that makes it easy to compile and test Erlang applications and releases. http://www.rebar3.org |
meta-erlang |
| refpolicy-mcs |
2.20210203+gitX |
MCS (Multi Category Security) variant of the SELinux policy |
meta-selinux |
| refpolicy-minimum |
2.20210203+gitX |
SELinux minimum policy |
meta-selinux |
| refpolicy-mls |
2.20210203+gitX |
MLS (Multi Level Security) variant of the SELinux policy |
meta-selinux |
| resource-retriever |
1.12.6-1 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros1-melodic |
| resource-retriever |
2.1.3-1 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros2-dashing |
| resource-retriever |
2.2.2-1 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros2-eloquent |
| resource-retriever |
2.3.4-1 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros2-foxy |
| resource-retriever |
2.5.0-1 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros2-rolling |
| resource-retriever |
1.12.6-1 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros1-noetic |
| resource-retriever |
2.5.0-2 |
This package retrieves data from url-format files such as http://, ftp://, package:// file://, etc., and loads the data into memory. The package:// url for ros packages is translated into a local file:// url. The resourse retriever was initially designed to load mesh files into memory, but it can be used for any type of data. The resource retriever is based on the the libcurl library. |
meta-ros2-galactic |
| retroarch-database |
2021+gitX |
RetroArch Database containing cheatcode files, content data files, etc. |
meta-libretro |
| retroarch-overlays |
2021+gitX |
RetroArch overlay collection |
meta-libretro |
| rmf-building-sim-ignition-pluginsblacklisted |
1.3.0-1 |
Ignition gazebo plugins for building infrastructure simulation |
meta-ros2-foxy |
| rmf-building-sim-ignition-pluginsblacklisted |
1.2.0-2 |
Ignition gazebo plugins for building infrastructure simulation |
meta-ros2-rolling |
| rmf-building-sim-ignition-pluginsblacklisted |
1.3.0-1 |
Ignition gazebo plugins for building infrastructure simulation |
meta-ros2-galactic |
| robot-activity-msgs |
0.1.1 |
This package contains messages used by robot_activity, such as node's state and error |
meta-ros1-melodic |
| ros-ign-interfaces |
0.221.2-1 |
Message and service data structures for interacting with Ignition from ROS2. |
meta-ros2-foxy |
| ros-ign-interfaces |
0.233.2-1 |
Message and service data structures for interacting with Ignition from ROS2. |
meta-ros2-rolling |
| ros-ign-interfaces |
0.233.2-1 |
Message and service data structures for interacting with Ignition from ROS2. |
meta-ros2-galactic |
| rosidl-typesupport-introspection-c |
0.7.10-1 |
Generate the message type support for dynamic message construction in C. |
meta-ros2-dashing |
| rosidl-typesupport-introspection-c |
0.8.3-1 |
Generate the message type support for dynamic message construction in C. |
meta-ros2-eloquent |
| rosidl-typesupport-introspection-c |
1.2.1-1 |
Generate the message type support for dynamic message construction in C. |
meta-ros2-foxy |
| rosidl-typesupport-introspection-c |
3.0.0-1 |
Generate the message type support for dynamic message construction in C. |
meta-ros2-rolling |
| rosidl-typesupport-introspection-c |
2.2.1-2 |
Generate the message type support for dynamic message construction in C. |
meta-ros2-galactic |
| rosidl-typesupport-introspection-cpp |
0.7.10-1 |
Generate the message type support for dynamic message construction in C++. |
meta-ros2-dashing |
| rosidl-typesupport-introspection-cpp |
0.8.3-1 |
Generate the message type support for dynamic message construction in C++. |
meta-ros2-eloquent |
| rosidl-typesupport-introspection-cpp |
1.2.1-1 |
Generate the message type support for dynamic message construction in C++. |
meta-ros2-foxy |
| rosidl-typesupport-introspection-cpp |
3.0.0-1 |
Generate the message type support for dynamic message construction in C++. |
meta-ros2-rolling |
| rosidl-typesupport-introspection-cpp |
2.2.1-2 |
Generate the message type support for dynamic message construction in C++. |
meta-ros2-galactic |
| roslib |
1.14.9-1 |
Base dependencies and support libraries for ROS. roslib contains many of the common data structures and tools that are shared across ROS client library implementations. |
meta-ros1-melodic |
| roslib |
1.15.8-1 |
Base dependencies and support libraries for ROS. roslib contains many of the common data structures and tools that are shared across ROS client library implementations. |
meta-ros1-noetic |
| rospy |
1.14.12-1 |
rospy is a pure Python client library for ROS. The rospy client API enables Python programmers to quickly interface with ROS <a href="http://ros.org/wiki/Topics">Topics</a>, <a href="http://ros.org/wiki/Services">Services</a>, and <a href="http://ros.org/wiki/Parameter Server">Parameters</a>. The design of rospy favors implementation speed (i.e. developer time) over runtime performance so that algorithms can be quickly prototyped and tested within ROS. It is also ideal for non-critical-path code, such as configuration and initialization code. Many of the ROS tools are written in rospy to take advantage of the type introspection capabilities. Many of the ROS tools, such as <a href="http://ros.org/wiki/rostopic">rostopic</a> and <a href="http://ros.org/wiki/rosservice">rosservice</a>, are built on top of rospy. |
meta-ros1-melodic |
| rospy |
1.15.13-1 |
rospy is a pure Python client library for ROS. The rospy client API enables Python programmers to quickly interface with ROS <a href="http://ros.org/wiki/Topics">Topics</a>, <a href="http://ros.org/wiki/Services">Services</a>, and <a href="http://ros.org/wiki/Parameter Server">Parameters</a>. The design of rospy favors implementation speed (i.e. developer time) over runtime performance so that algorithms can be quickly prototyped and tested within ROS. It is also ideal for non-critical-path code, such as configuration and initialization code. Many of the ROS tools are written in rospy to take advantage of the type introspection capabilities. Many of the ROS tools, such as <a href="http://ros.org/wiki/rostopic">rostopic</a> and <a href="http://ros.org/wiki/rosservice">rosservice</a>, are built on top of rospy. |
meta-ros1-noetic |
| rosrt |
1.0.25 |
rosrt provides classes for interfacing with ROS from within realtime systems, such as realtime-safe Publisher and Subscriber classes. |
meta-ros1-melodic |
| rosrt |
1.0.25-1 |
rosrt provides classes for interfacing with ROS from within realtime systems, such as realtime-safe Publisher and Subscriber classes. |
meta-ros1-noetic |
| rqt-py-commonblacklisted |
0.5.2-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros1-melodic |
| rqt-py-commonblacklisted |
1.0.7-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros2-dashing |
| rqt-py-commonblacklisted |
1.0.5-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros2-eloquent |
| rqt-py-commonblacklisted |
1.1.2-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros2-foxy |
| rqt-py-commonblacklisted |
1.1.2-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros2-rolling |
| rqt-py-commonblacklisted |
0.5.2-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros1-noetic |
| rqt-py-commonblacklisted |
1.1.2-1 |
rqt_py_common provides common functionality for rqt plugins written in Python. Despite no plugin is provided, this package is part of the rqt_common_plugins repository to keep refactoring generic functionality from these common plugins into this package as easy as possible. Functionality included in this package should cover generic ROS concepts and should not introduce any special dependencies beside "ros_base". |
meta-ros2-galactic |
| rqt-reconfigureblacklisted |
0.5.4-1 |
This rqt plugin succeeds former dynamic_reconfigure's GUI (reconfigure_gui), and provides the way to view and edit the parameters that are accessible via dynamic_reconfigure.<br/> <br/> (12/27/2012) In the future, arbitrary parameters that are not associated with any nodes (which are not handled by dynamic_reconfigure) might become handled. However, currently as the name indicates, this pkg solely is dependent on dynamic_reconfigure that allows access to only those params latched to nodes. |
meta-ros1-melodic |
| rqt-reconfigureblacklisted |
0.5.4-1 |
This rqt plugin succeeds former dynamic_reconfigure's GUI (reconfigure_gui), and provides the way to view and edit the parameters that are accessible via dynamic_reconfigure.<br/> <br/> (12/27/2012) In the future, arbitrary parameters that are not associated with any nodes (which are not handled by dynamic_reconfigure) might become handled. However, currently as the name indicates, this pkg solely is dependent on dynamic_reconfigure that allows access to only those params latched to nodes. |
meta-ros1-noetic |
| rqt-robot-dashboardblacklisted |
0.5.7 |
rqt_robot_dashboard provides an infrastructure for building robot dashboard plugins in rqt. |
meta-ros1-melodic |