On Thursday 18 November 2010 13:15:52 Konrad Banachowicz wrote: > 2010/11/18 S Roderick @mac.com> > Git allows you to bypass this issue completely. Track KDL's master branch, > use your own topic branch for your modifications to KDL, and then publish > this branch so that the KDL maintainer's can pull it in. When your changes > are integrated to KDL (some time in the future) then your next update of > KDL will grab them, rebase your topic branch, and continue development. > You get the benefit of always having _your_ latest and greatest, and > everyone else gets the benefit of your contributions. Yes i understand the > work-flow but i use ROS build system for my components which grab KDL from > ROS distribution. I can create overlay for KDL in ROS but then everyone > who want to build my stack need overlay too. There is an orocos_kdl package in our orocos_kinematics_dynamics stack that tracks the trunk of kdl. Ruben