Thanks, Ken and Tully! For all you other ROS + OpenRAVE users out there: I also noticed that Rosen has indeed provided install files for using ROS with OpenRAVE: http://openrave.programmingvision.com/index.php/Installation#ROS_Installation I'll be sure to install union of the suggested packages. Thanks, Garratt On Tue, Apr 13, 2010 at 5:35 PM, Tully Foote wrote: > Garratt, > The rosinstall file > http://www.ros.org/rosinstalls/boxturtle_wg_all.rosinstall is basically > the same as the old externals. It will pull everything against boxturtle, > including the unstable stuff you were using all at once. > > Tully > > > On Tue, Apr 13, 2010 at 2:30 PM, Ken Conley wrote: > >> Hi Garratt, >> >> The discouragement of wg-ros-pkg/all is related to the fact that you >> mention two components that have not been officially released yet, and >> in the case of semantic_mapping, is being rewritten (as pcl). We've >> had a lot of confusion from users in the past who get exposed to both >> stable and unstable code, the latter which sometimes disappears and, >> like a phoenix, reborn. This is a transitional period, and those who >> were using stuff we haven't released yet will find themselves >> straddling a divide. We're racing forward as fast as we can to fill in >> this gap. >> >> In the directory: >> >> http://www.ros.org/rosinstalls/ >> >> you will find many of the rosinstall configs you request. In >> particular, these point to the unreleased components: >> >> http://www.ros.org/rosinstalls/wg_boxturtle_devel.rosinstall >> http://www.ros.org/rosinstalls/wg_latest_devel.rosinstall >> >> You can either use rosinstall, or you can just look in the config file >> for the relevant URL. I'm guessing you want the boxturtle trunks. >> >> As I mentioned before, semantic_mapping is being reborn as pcl in the >> point_cloud_perception stack, which is only available in the unstable >> 'latest' distribution (only for the strong of heart). As for >> openrave_planning, I know that Rosen is working on that actively. The >> main issue there is it depends on packages that aren't released, and, >> in one case, removed in latest. I defer to Rosen as to the best >> configuration for using OpenRAVE with ROS. >> >> - Ken >> >> >> >> On Tue, Apr 13, 2010 at 2:08 PM, garratt gallagher >> wrote: >> > I installed ROS a few months ago, and was working out of the >> > >> > https://code.ros.org/svn/wg-ros-pkg/all >> > >> > directory. Specifically, I'm using openrave related packages, and some >> > packages in semantic_mapping. >> > >> > I'm now installing ROS on another computer and ran into the following >> > problems: >> > 1) the openrave-planning stack is not supported in turtlebox, or latest. >> (in >> > the pre-compiled binaries) How do stacks make it into the 'ubuntu >> > packagable' status, and can I influence this/help? >> > 2) given that the packages I want are not available as binaries, where >> is >> > the best place to check them out? >> > >> > https://code.ros.org/svn/wg-ros-pkg/externals/boxturtle/ >> > >> > does not have them (ex: openrave-planning stack). Should I just >> continue to >> > use https://code.ros.org/svn/wg-ros-pkg/all , despite Ken's strong >> > encouragement? I noticed that this is still encouraged by >> > http://www.ros.org/wiki/Source%20code. Poking around the repo, there >> are >> > many different copies of the code, and it is not immediately obvious >> which >> > branches are being developed/stable/abandoned. >> > >> > In general, it would be nice to have some sort of spreadsheet/table what >> has >> > the packages (or stacks) and where (in svn or via a binary) they might >> be >> > found, and how stable it would be there. (ok, that does sound like a lot >> of >> > work) >> > >> > 3) Assuming that the only way to get certain packages is through >> > rosinstall/svn co, maybe the install wiki could include rosintall files >> for >> > 'unreleased' packages? >> > >> > After about an hour of poking around the wiki and the svn repos, I think >> > I've found how to proceed (just using wg-ros-pkg/all. I also looked in >> the >> > wiki's history, to find the page that I had originally used when >> installing >> > ROS) >> > >> > Overall, I applaud the move to more stable packages, using stack, etc. >> I've >> > used ROS for over a year now, and am excited that it has finally reached >> > package-level stability. However, I'm troubled by how difficult it is >> to >> > run what used to be a normal install. >> > >> > Thanks >> > Garratt >> > >> > >> > >> > On Tue, Mar 9, 2010 at 6:35 PM, Ken Conley >> wrote: >> >> >> >> Hi Lorenz, >> >> >> >> As Tully notes, the debian-building infrastructure is still in its >> >> baby stages. The source code for it is in various packages within >> >> "ros_installers": >> >> >> >> https://code.ros.org/svn/ros/installers/trunk >> >> >> >> There's a lot of extra, unused stuff in there, and there aren't >> >> instructions on setting up your own infrastructure yet. >> >> >> >> - Ken >> >> >> >> On Tue, Mar 9, 2010 at 2:23 PM, Tully Foote >> >> wrote: >> >> > Hi Lorenz, >> >> > If you used rosinstall to install to ~/foo. It is recommended to use >> >> > ~/rosinstall -u ~/foo. This will go through and update all your >> source >> >> > checkouts in the rosinstall file. As well as svn it also supports >> bzr >> >> > and >> >> > git checkouts. >> >> > >> >> > As for the debian building infrastructure. Right now it's not >> >> > structured in >> >> > a way that a releasing it would be useful. In the future we do plan >> to >> >> > streamline it and make it available. >> >> > >> >> > Tully >> >> > >> >> > 2010/3/9 Lorenz Mösenlechner >> >> >> >> >> >> Hi, >> >> >> >> >> >> great work! >> >> >> >> >> >> Is there already a tutorial on how to build these debian packages? >> We >> >> >> are still using debian lenny and I'm curious if it would be hard for >> >> >> us to build the packages for our platform. >> >> >> >> >> >> And as a second remark, I couldn't find documentation on how to >> update >> >> >> the new installation when it's not based on debian packages but the >> >> >> svn repositories. Since it is discouraged to use the 'all' >> repository >> >> >> now and the rosinstall script just checks out lot's of small >> >> >> repositories, going into every dir and doing an svn up seems to be >> >> >> quite cumbersome. I found an update option in rosinstall, but I >> >> >> couldn't find any documentation for it. But is it the recommended >> way >> >> >> to do the update? >> >> >> >> >> >> Thanks, >> >> >> Lorenz >> >> >> >> >> >> >> >> >> > Our first ROS Distribution release is here: Box Turtle. You can >> read >> >> >> > our announcement at: >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> http://www.ros.org/news/2010/03/ros-distributions-box-turtle-release.html >> >> >> > >> >> >> > Kudos to Morgan Quigley for bringing apt-get to ROS! >> >> >> > >> >> >> > For developers, we want to highlight a few more things that come >> with >> >> >> > this release. The first is that we are providing support (i.e. bug >> >> >> > fixes) for the 1.0 stacks in this release, which cover most of our >> >> >> > core capabilities, like navigation. >> >> >> > >> >> >> > Second, our bleeding edge development will be in the "Latest" >> >> >> > release, >> >> >> > out of which we will hatch "C Turtle". >> >> >> > >> >> >> > We strongly encourage transitioning off of: >> >> >> > >> >> >> > https://code.ros.org/svn/wg-ros-pkg/all/ >> >> >> > >> >> >> > as it links against these bleeding-edge versions. Our ROS >> >> >> > installation >> >> >> > instructions [1] provide 'rosinstall' files with several >> >> >> > configurations for SVN checkout. You can also fetch all of our >> >> >> > released stacks (including PR2 stacks) from: >> >> >> > >> >> >> > https://code.ros.org/svn/wg-ros-pkg/externals/boxturtle/ >> >> >> > >> >> >> > Third, we want to say thank you, especially to the early adopters, >> >> >> > for >> >> >> > sticking with us as ROS went through its growing pains to reach >> this >> >> >> > first distribution. We've done our best to take your feedback >> about >> >> >> > stability, documentation, and tutorials, and tried to roll it into >> >> >> > our >> >> >> > first ROS distribution. There were many deprecations and changes >> >> >> > along >> >> >> > the way, but we've now arrived at a new release process that >> >> >> > identifies stable libraries and provides an easier migration >> process >> >> >> > forward. We hope this will provide what you've been looking for. >> If >> >> >> > not, we're always listening for feedback. >> >> >> > >> >> >> > Finally, to repeat an administrative note, >> wg-ros-pkg/trunk/sandbox >> >> >> > has been emptied and deprecated packages deleted. We've created a >> >> >> > boxturtle branch of wg-ros-pkg/trunk [2] that you can checkout on >> top >> >> >> > of Box Turtle. >> >> >> > >> >> >> > There are a lot of cool things in the works for C Turtle. In the >> >> >> > meantime, enjoy Box Turtle and let us know what you think! >> >> >> > >> >> >> > -- your friendly neighborhood ROS turtle hatchery >> >> >> > >> >> >> > [1]: http://ros.org/wiki/ROS/Installation >> >> >> > [2]: >> https://code.ros.org/svn/wg-ros-pkg/branches/trunk_boxturtle/ >> >> >> > _______________________________________________ >> >> >> > ros-users mailing list >> >> >> > ros-users@code.ros.org >> >> >> > https://code.ros.org/mailman/listinfo/ros-users >> >> >> > >> >> >> >> >> >> -- >> >> >> Lorenz Mösenlechner | moesenle@in.tum.de >> >> >> Technische Universität München | Boltzmannstr. 3 >> >> >> 85748 Garching bei München | Germany >> >> >> http://ias.cs.tum.edu/ | Tel: +49 (89) 289-17750 >> >> >> >> >> >> _______________________________________________ >> >> >> ros-users mailing list >> >> >> ros-users@code.ros.org >> >> >> https://code.ros.org/mailman/listinfo/ros-users >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Tully Foote >> >> > Systems Engineer >> >> > Willow Garage, Inc. >> >> > tfoote@willowgarage.com >> >> > (650) 475-2827 >> >> > >> >> > _______________________________________________ >> >> > ros-users mailing list >> >> > ros-users@code.ros.org >> >> > https://code.ros.org/mailman/listinfo/ros-users >> >> > >> >> > >> >> _______________________________________________ >> >> ros-users mailing list >> >> ros-users@code.ros.org >> >> https://code.ros.org/mailman/listinfo/ros-users >> > >> > >> > _______________________________________________ >> > ros-users mailing list >> > ros-users@code.ros.org >> > https://code.ros.org/mailman/listinfo/ros-users >> > >> > >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users >> > > > > -- > Tully Foote > Systems Engineer > Willow Garage, Inc. > tfoote@willowgarage.com > (650) 475-2827 > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > >