Some related material: http://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html#s-maintscripts On Fri, May 17, 2013 at 11:27 AM, William Woodall wrote: > Or you can change the permissions of the executable (setuid or setcap) in > a post install hook. > > So you would write a script which does this, from source I would run this > script manually after building and from debian this script would be run as > a post install hook. > > I haven't setup a post install hook before, but you should be able to do > this in the debian folder of the `debian/groovy/` branch in > your release repository (don't for get to run bloom again after the change). > > Running `git-buildpackage -uc -us` while on the appropriate debian tag > (something like `debian/ros-groovy-youbot-driver_0.1.2-0_precise`) will > build debs you can test from your release repository. The debs will be > created one folder up. > > Hope that helps, > > > > On Fri, May 17, 2013 at 11:12 AM, Toris, Russell Charles wrote: > >> I had added libcap2-bin yesterday. >> >> Agreed to all of these but I'm not sure how to get around it. We are >> attempting to have the existing base youbot software released and the >> decision to need setcap was made there to communicate over various ethernet >> devices on the robot. The alternative is to require you to run the >> executables as root which is equally bad. >> >> To follow up with Tully, I think you are right about setcap not >> transferring so now I'm out of ideas on what to do here. Hm.... >> >> >> -- >> Russell Toris >> Graduate Student | WPI Department of Computer Science >> rctoris@wpi.edu | http://users.wpi.edu/~rctoris/ >> >> ________________________________ >> From: ros-release-bounces@code.ros.org [ros-release-bounces@code.ros.org] >> on behalf of William Woodall [william@osrfoundation.org] >> Sent: Friday, May 17, 2013 2:11 PM >> To: Jack O'Quin >> Cc: ros-release@code.ros.org >> Subject: Re: [Ros-release] sudo not found? >> >> It should probably be a buildtool_depend, but either way using sudo >> inside CMake seems really wacky, how am I supposed to build this from >> source on a machine where I don't have sudo? >> >> I am not sure if there is a better alternative, but you should consider >> separating the permissions settings and building. Ideally this would be a >> post install hook action or a manual step after building for source install. >> >> Do other projects require sudo at build time for this sort of action? >> >> >> On Fri, May 17, 2013 at 11:07 AM, Jack O'Quin > > wrote: >> >> On Fri, May 17, 2013 at 12:50 PM, Tully Foote > > wrote: >> HI Russell, >> >> The first answer is yes, if you need sudo you need to add it as a >> dependency. The builds on the farm will only build with your declared >> dependencies. The prerelease has a minimal bootstrap which gives you >> command line capabilities for debugging presumably includes sudo for that >> purpose.) You will probably also want to add a build-depend rosdep rule >> for libcap2-bin to make sure the setcap is installed. >> >> Since they run on the build machine, shouldn't they use >> ? >> -- >> joq >> >> _______________________________________________ >> Ros-release mailing list >> Ros-release@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-release >> >> >> >> >> -- >> William Woodall >> ROS Development Team >> william@osrfoundation.org >> http://williamjwoodall.com/ >> > > > > -- > William Woodall > ROS Development Team > william@osrfoundation.org > http://williamjwoodall.com/ > -- William Woodall ROS Development Team william@osrfoundation.org http://williamjwoodall.com/