On Fri, May 17, 2013 at 11:39 AM, Toris, Russell Charles <
rctoris@wpi.edu>wrote:
> Awesome, thanks William! This is exactly what I needed. I'll add a
> postinst script to run setcap.
>
> Two questions for you:
>
>
> 1. Where should I list libcap-bin in my package.xml dependencies so
> that it will be installed on the user's machine instead of the build farms?
>
You should run_depend on it.
> 2. Can you elaborate on what you mean by "don't forget to run bloom
> again after the change"? What I understand is I run a release,
> bloom-release --ros-distro groovy youbot_driver groovy and then before
> pushing, I add my postinst file to the debian folder of the
> debian/groovy/youbot_driver branch, and then push it up to the release
> repo. Is this correct?
>
This is what I would do:
1. clone your release repo manually and go into that directory
2. run `git-bloom-release groovy` (only if you haven't run it for this
version)
3. change to the branch you want to patch `git checkout
debian/groovy/youbot_driver`
4. Make your changes and commit `git add . && git commit -am "some
message"`
5. Export the patches `git-bloom-patch export` (shouldn't be required,
just to be safe)
6. I like to go back to master `git checkout master` (shouldn't be
required)
7. run the bloom release again `git-bloom-release groovy` (this makes
your changes propagate to the leaf tags which the build farm uses)
8. Go to the resulting tag `git checkout
debian/ros-groovy-youbot-driver_0.1.3-1_precise` (something like that)
9. Build the deb `git-buildpackage -uc -us`
10. Test it `cd .. && dpkg -i *.deb`
Some of those commands might need tweaking as I just listed them off the
top of my head.
>
> Thanks!!
>
>
> Russell
>
> --
> Russell Toris
> Graduate Student | WPI Department of Computer Science
> rctoris@wpi.edu | http://users.wpi.edu/~rctoris/
>
> ________________________________
> From: William Woodall [william@osrfoundation.org]
> Sent: Friday, May 17, 2013 2:34 PM
> To: Toris, Russell Charles
> Cc: Jack O'Quin; ros-release@code.ros.org
> Subject: Re: [Ros-release] sudo not found?
>
> 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 <
> william@osrfoundation.org<mailto:william@osrfoundation.org>> 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/<package_name>` 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 <rctoris@wpi.edu
> <mailto:rctoris@wpi.edu>> 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<mailto:rctoris@wpi.edu> | http://users.wpi.edu/~rctoris/
>
> ________________________________
> From: ros-release-bounces@code.ros.org<mailto:
> ros-release-bounces@code.ros.org> [ros-release-bounces@code.ros.org
> <mailto:ros-release-bounces@code.ros.org>] on behalf of William Woodall [
> william@osrfoundation.org<mailto:william@osrfoundation.org>]
> Sent: Friday, May 17, 2013 2:11 PM
> To: Jack O'Quin
> Cc: ros-release@code.ros.org<mailto: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 <jack.oquin@gmail.com
> <mailto:jack.oquin@gmail.com><mailto:jack.oquin@gmail.com<mailto:
> jack.oquin@gmail.com>>> wrote:
>
> On Fri, May 17, 2013 at 12:50 PM, Tully Foote <tfoote@osrfoundation.org
> <mailto:tfoote@osrfoundation.org><mailto:tfoote@osrfoundation.org<mailto:
> tfoote@osrfoundation.org>>> 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 <buildtool_depend>?
> --
> joq
>
> _______________________________________________
> Ros-release mailing list
> Ros-release@code.ros.org<mailto:Ros-release@code.ros.org><mailto:
> Ros-release@code.ros.org<mailto:Ros-release@code.ros.org>>
> https://code.ros.org/mailman/listinfo/ros-release
>
>
>
>
> --
> William Woodall
> ROS Development Team
> william@osrfoundation.org<mailto:william@osrfoundation.org><mailto:
> william@osrfoundation.org<mailto:william@osrfoundation.org>>
> http://williamjwoodall.com/
>
>
>
> --
> William Woodall
> ROS Development Team
> william@osrfoundation.org<mailto:william@osrfoundation.org>
> http://williamjwoodall.com/
>
>
>
> --
> William Woodall
> ROS Development Team
> william@osrfoundation.org<mailto:william@osrfoundation.org>
> http://williamjwoodall.com/
>
--
William Woodall
ROS Development Team
william@osrfoundation.org
http://williamjwoodall.com/
(text/plain)