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