This is a good request; unfortunately it's more complicated than it seems. The typical SVN layout has become more complicated since the humble beginnings of roslocate. I tried to implement adding the URLs to the wiki a couple of weeks ago and ran into several issues: 1) Addition of git and bzr support 2) Released vs. unreleased code, plus stacks 3) Multiple releases of a package (i.e. boxturtle vs. latest) Right now, tools like Browse and the wiki work at the package level; they have no idea about #2 and #3. It's really only the Stack releases page that has enough knowledge right now to give the best URL to a package (i.e. I want the development branch, the boxturtle tag, the versioned tag). In the case that motivated this example, Andreas tried to get point_cloud_mapping, which is currently being torn apart to make PCL and is also built on top of a lot of unstable/deprecated code. All of the code is stuff that we're intentionally trying to hide away because we don't want people to be confused by "should I download ANN or ann", as well as "why am I now downloading deprecated_msgs"? So, apologies Andreas -- there's really not a good solution for you right now. Given that you are using a deb-based install of ROS Box Turtle, my best recommendation for you is to probably checkout our old "Box Turtle" sandbox here: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_boxturtle/ That will give you a lot of packages you don't need, but it does contain all of the packages you wanted at their Box Turtle version. The new point_cloud_perception stack should alleviate this particular problem when it matures; unfortunately we didn't have time to include it in Box Turtle. - Ken On Tue, Mar 16, 2010 at 8:12 AM, Jack O'Quin wrote: > On Tue, Mar 16, 2010 at 9:59 AM, Tully Foote wrote: >> The svn urls for released stacks are available under the "Releases" link >> in the menu. >> >> For example http://www.ros.org/wiki/common >> http://www.ros.org/wiki/common/Releases > > With the advent of boxturtle, these are seldom needed. For me, it's > usually the more obscure packages I can't find. If it's late and I'm > tired, I sometimes forget the excellent "roslocate svn " > command. New users may not know about it. > > For new ROS users, automatically including the source URL in every > package page would be good. > -- >  joq > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >