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 |
You should really try to get your fix accepted into the upstream repository, and released through the official build farm.
It's possible to build debs by setting up a release repository using bloom and then manually invoking the deb build process, but if you install those debs, there's no guarantee that they'll persist across upgrades. For example, if the upstream rqt releases a new version with a higher version number than the deb you build, it will automatically replace your custom deb when someone runs 'apt-get upgrade'
The other alternative is not to try to build debs at all; just add your custom rqt package to your catkin workspace, and it will always override the system 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.
