The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The best solution would be to submit your patches to the package maintainer(s) and let them be added to the official sources. Another solution would be to fork the package(s) under a different name, and keep developing them on your own.
You can also make a local copy of the package(s) in the same directory where you keep your own stuff. If this location comes before the /opt/ros/VERSION/stacks path in your ROS_PACKAGE_PATH, all ROS tools will use your edited copy instead of the distributed version.
However, this is essentially a fork where you keep the old name, creating all sorts of compatibility problems. I'd advise against this for anything else than a few added debugging outputs or an emergency fix if you can't wait for an upgraded version.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
