Commit Graph

9 Commits

Author SHA1 Message Date
Lukas Bulwahn 8249cc8dd5 improving formatting after automated style check
After running oe-stylize.py on all recipes in recipes-ros, this
commit improves the formatting of some recipes.

To achieve this, I executed these commands in recipes-ros:
find . -name *.bb | sed 's#\(.*\)#./oe-stylize.py \1 > \1_sanitized#' | sh
find . -name *.bb | sed 's#\(.*\)#diff -Naur \1 \1_sanitized#' | sh > diffs

Then, I manually inspected the diffs file, and improved the
recipes.

For the DESCRIPTION line in the addressed recipes, the line width
of 100 characters was chosen, as the LIC_FILES_CHKSUM line and
SRC_URI line usually are also around about 100 characters long.
Hence, choosing a shorter line width, e.g. 80 characters, would
have only created more line breaks, but not reduced the need to
use a file viewer with which 100 characters line width can be
displayed. For the github file and diff viewer and most editors
on reasonably-sized screens, 100 character line width is no
problem.
2014-08-18 06:51:31 +02:00
Lukas Bulwahn 080fa48ab4 ros-control: adding patch accepted upstream 2014-08-04 07:06:39 +02:00
Lukas Bulwahn 21f7799ee9 adding Upstream-Status remarks to patches in recipes-ros
This commit further adds a simple fix to the patch for the ros-comm
repository.
2014-04-24 07:03:36 +02:00
Lukas Bulwahn fb365e9f35 ros-control: updating to 0.7.2 2014-04-09 07:51:18 +02:00
Lukas Bulwahn 3bb1279910 ros-control: removing rostest dependency 2014-03-20 08:01:52 +01:00
Lukas Bulwahn 0ad53adc73 ros-control: updating to 0.6.0 2014-03-04 17:28:37 +01:00
Lukas Bulwahn 0ee09e835b controller-manager-msgs: address issue #170 2013-10-15 08:43:10 +02:00
Lukas Bulwahn 45038e3423 ros-control: updating to 0.5.8
The ros-control recipes are updated to 0.5.8 to be in line with
74f48fa69e/hydro/release.yaml.
The applied patches are merged upstream in 0.5.8 and were removed.
2013-10-14 11:08:58 +02:00
vmayoral 0f0e8148ef ros-control: recipes added.
A set of packages that include controller interfaces, controller managers,
transmissions, hardware_interfaces and the control_toolbox.

The ros_control packages takes as input the joint state data from your robot's
actuator's encoders and an input set point. It uses a generic control loop
feedback mechanism, typically a PID controller, to control the output,
typically effort, sent to your actuators. ros_control gets more complicated
for physical mechanisms that do not have one-to-one mappings of joint
positions, efforts, etc but theses scenarios are accounted for using
transmissions.
2013-09-22 16:17:09 +02:00