Source: ros-one-mbf-abstract-nav
Section: misc
Priority: optional
Maintainer: Sebastian Pütz <spuetz@uos.de>
Build-Depends: debhelper (>= 9.0.0), ros-one-actionlib, ros-one-actionlib-msgs, ros-one-catkin, ros-one-dynamic-reconfigure, ros-one-geometry-msgs, ros-one-mbf-abstract-core, ros-one-mbf-msgs, ros-one-mbf-utility, ros-one-nav-msgs, ros-one-roscpp, ros-one-std-msgs, ros-one-std-srvs, ros-one-tf, ros-one-xmlrpcpp
Homepage: http://wiki.ros.org/move_base_flex
Standards-Version: 3.9.2

Package: ros-one-mbf-abstract-nav
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ros-one-actionlib, ros-one-actionlib-msgs, ros-one-dynamic-reconfigure, ros-one-geometry-msgs, ros-one-mbf-abstract-core, ros-one-mbf-msgs, ros-one-mbf-utility, ros-one-nav-msgs, ros-one-roscpp, ros-one-std-msgs, ros-one-std-srvs, ros-one-tf, ros-one-xmlrpcpp
Description: The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF).
 The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions.
