ros-planning/moveit_metapackages

DEPRECATED - see https://github.com/ros-planning/moveit

moveit_metapackages

This repository includes metapackages for installation variants of MoveIt!.

moveit_metapackages's Issues

Deprecate moveit_metapackages repo

• For Indigo, multiple repos host metapackages for MoveIt! core libraries.
  • moveit in moveit repo.
  • moveit_full/_pr2 in moveit_metapackages repo.
• For Jade onward, we won't release moveit_full/_pr2 metapackages ros-planning/moveit_ros#692 (comment)

Why not deprecate this repo and move all existing metapackages to indigo-devel branch on moveit repo?

Moving metapackages into moveit repo can also prevent release maintainers from working on two different releases.

Steps to be made:

1. Merge existing PR (currently only #10)
2. Import all the existing metapackages on this repo into the top level dir of moveit repo. --> I ros-planning/moveit#422, JK ros-planning/moveit#436
3. Deprecate notice for this repo (well actually deprecated notice is already posted at the top page of this repo).
4. Open a new PR on rosdistro to move all the existing metapackages into the entry that is rooted on moveit repo. --> ros/rosdistro#13767 --> NG. Need to bloom #11 (comment)

Metapackage for deploying MoveIt! on robots

Out of low importance.

moveit metapackage includes moveit_setup_assistant. While having it installed with a single command is convenient for developers, installing it on the robots might not be necessary.
To even improve deployment process onto robots, having a package suite that depends only on runtime packages might be convenient. moveit_full with the current list of packages seems to serve for this purpose but its name doesn't. Something like moveit_runtime?

Remove or fix moveit_source_build_deps

moveit_source_build_deps is really an odd metapackage, if it isn't used anymore it should be removed, if it is used, it should be updated to not depend on packages which are not part of this metapackage.

This results in this metapackage showing up on random wiki pages:

http://ros.org/wiki/dynamic_reconfigure
http://ros.org/wiki/actionlib
http://ros.org/wiki/control_msgs
....

The list goes on.

These metapackages incorrectly depend on core packages

These metapackages directly depend on things like rospy, which is incorrect, it should instead depend on ros_comm or some other metapackage to pull these in. This style of including produces incorrect groupings on the wiki:

http://ros.org/wiki/rospy

Release into Jade

Raised ros-planning/moveit_ros#692

If write access to this repo and release-repo is given, I can work on it.

Release to Indigo

ros-indigo-moveit-full does not seem to exist yet, needs to be released I think

build dependency to pr2-mechanism-msgs

I'm not sure if it fits here, but the ubuntu 12.4 package

ros-groovy-moveit-source-build-deps

seems to miss a dependency to

ros-groovy-pr2-mechanism-msgs

After manually installing this package, the installation as described in

http://moveit.ros.org/installation_source.html

succeeded.

missing ros-groovy-pr2-mechanism dependency

Compiling MoveIt from source as indicated on the wiki throws an error if ros-groovy-pr2-mechanism is not installed. Therefore, this should be included in the ros-groovy-moveit-source-build-deps or the pr2_moveit` package should not be included by default in the MoveIt repos (this also makes sense to me since MoveIt should be robot agnostic)