ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Stack concept removed from distros since Groovy, how will be the migration? [closed]

asked 2012-11-28 14:49:38 -0600

updated 2013-04-30 08:17:24 -0600

130s gravatar image

Reading from release notes and tutorials on Groovy, I've found that stack concept will be removed (or changed by metapackages) and rosbuild tool will be replaced by catkin.

I know that I can migrate my packages and applications making changes to some files, filenames, etc.

But, What would happen with applications pre-groovy? I mean, all stacks (now metapackages) will be migrated to the new filesystem? Must I install them and migrate them? or Will be there two versions of metapackages in repositories, one as stack and one as metapackage? Updates in software will be just for metapackages?

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by georgebrindeiro
close date 2012-12-03 11:48:12

1 Answer

Sort by ยป oldest newest most voted

answered 2012-11-28 23:37:28 -0600

KruseT gravatar image

updated 2012-12-02 01:46:18 -0600

ROS Groovy still allows you to keep your stacks as they are. It is however recommended that you move to the catkin build system and meta-packages, because support for stacks (for the rosmake command) is intended to be dropped in some future version of ROS.

So catkin is introduced as a tool that users can use instead of rosbuild, but rosbuild currently still exists. Thus, not all stacks will be migrated at once.

If you install ROS Groovy, you will get some packages with stacks, and some with meta-packages, but never the same package with both stack and meta-package.

If you do the migration, you can keep a branch of your software in a repository for pre-fuerte users. Many ROS packages now define branches like "fuerte-devel", "groovy-devel" and so on, where groovy-devel will use catkin, and fuerte-devel still uses rosbuild.

Whether old branches will still get updates depends on individual maintainers. But expect that developers will spend most of their time on updates for the latest ROS distribution. So if a group of packages has been migrated from rosbuild to catkin, it is likely there will be less activity on maintaining the rosbuild branch of those packages.

edit flag offensive delete link more

Question Tools


Asked: 2012-11-28 14:49:38 -0600

Seen: 1,894 times

Last updated: Dec 02 '12