Differences between revisions 1 and 53 (spanning 52 versions)
Revision 1 as of 2015-05-14 15:49:18
Size: 1682
Editor: ?LeopoldPalomo
Comment: Initial input. It's a draft
Revision 53 as of 2022-05-08 22:18:07
Size: 3757
Editor: ?JochenSprickerhof
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
The official ROS page shows that as platform supported are: Ubuntu and Ubuntu (armhf). Also, it's supported from source. == Shortcuts about ROS in Debian ==
Line 3: Line 3:
Install ROS is a Debian box is not a trivial thing. OSRF(current ROS maintainer) provides packages for Ubuntu generated using a tool (bloom). They are installed in /opt/ros/$rosversion and doesn't obey FHS. This point has been discussed in the past [ 1,2], but and some efforts has been done to accomplish it, but it's implementation has show some drawbacks hidden in the ROS implementation.  * [[ DebianScience/Robotics/ROS/Packages | Status of the current native packages ]]
 * [[ DebianScience/Robotics/ROS/DebianRoboticsPackages| Debian for Robotics packages ]]
 * [[ DebianScience/Robotics/ROS/OnBuster | Installing ROS in Buster ]]
 * [[ DebianScience/Robotics/ROS/DebianPackages | What are the native packages ?]]
Line 5: Line 8:
Also, some GNU/Linux distributions are more strict than other, but for example Debian requires that any library installed has defined a SONAME. == Introduction ==
Line 7: Line 10:
The initiative of packaging ROS for Debian was initiated by Thomas Moulard for the debian-science group and continued by Jochen Sprickerhof and Leopold Palomo-Avellaneda. The sources of the packages are hosted here. Robot Operating System (ROS or ros) is an open-source robotics middleware suite. Although ROS is not an operating system but a collection of software frameworks for robot software development, it provides services designed for a heterogeneous computer cluster such as hardware abstraction, low-level device control, implementation of commonly used functionality, message-passing between processes, and package management [[[https://en.wikipedia.org/wiki/Robot_Operating_System| Wikipedia]]. ROS has two main versions: ROS1 and ROS2.
Line 9: Line 12:
We have created a set of packages of the core of ROS plus other extras. Currently (May 2015) we have more than half of the packages of desktop_full installation. The packages have been build for: Debian Jessie and Stretch(sid-testing) and Ubuntu Trusty. ROS is released as distributions, also called “distros”, with more than one ROS distribution supported at a time. Check upstream [[ http://www.ros.org | web ]] for more information. This framework consists of about 1600 packages or projects that give a myriad of benefits for those of us who work in the field of robotics.
Line 11: Line 14:
All the packages comes from the same sources and we just have recompiled in a clean environment for the selected distros. They are more or less lintian clean, but we are still under development. They obey FHS and have the needed SONAMES. The aim of all this effort is to upload them as official packages in Debian.
Line 13: Line 15:
All the installations need the packages created and some part compiled. Also, with a few steps in the environment. With the base of the packages, you can compile almost all the packages created for ROS. To use them try: == ROS1 installation ==

The official [[http://wiki.ros.org/noetic/Installation|ROS page]] shows that the platforms supported are:

 * Ubuntu Focal amd64 armhf arm64
 * Debian Buster amd64 arm64

The rest of the platforms are experimental. In case you are running Bullseye or Testing/Unstable you cannot use Upstream packages.

The packages they provide are self-generated and do not feet most the rules of the Debian project. Each package, for [[ https://github.com/ros-visualization/qt_gui_core/tree/melodic-devel/qt_gui |example]], contains a package.xml file that among other things, it contains what its dependencies are for, to build and to run the package. Upstream provides a tool [[ http://wiki.ros.org/bloom | python3-bloom ]] , that it is in the [[ https://packages.debian.org/bullseye/python3-bloom | archive]] which generates a debian directory with necessary files to run debuild from that debian directory. It's a rudimentary package that for example, provides the *.pyc files!!.

=== There are another options? ===

Yes!! A big yes. The answer depend on the number of packages that you need of ROS1. For the majority of the users, that only needs the core libraries and some applications you can use your Debian distro without any other stuff. The necessary packages are the Debian native packages and you can obtain more information [[ DebianScience/Robotics/ROS/DebianPackages | here ]]. They began to appear in the archive since Debian Stretch.

=== Your versions in Stable are outdated ===

Yes, if you are here you know how Debian works. However, you can use [[ DebianScience/Robotics/ROS/DebianRoboticsPackages| Debian for Robotics packages ]] that has backported versions of Unstable and some plus to use in Debian Stable.

=== But, I need ros-foo that is wonderful and it is no packaged ===

You have several options. For instance, if you are running Debian Buster/Bullseye/Testing/Unstable) you can use the [[ DebianScience/Robotics/ROS/DebianPackages | native packages ]] and complete the rest. [[ DebianScience/Robotics/ROS/OnBuster | Here ]] there is an example of how to do it.

If you are running Debian Bullseye, with the [[ DebianScience/Robotics/ROS/DebianRoboticsPackages| Debian for Robotics packages ]] you can use [[https://salsa.debian.org/robotics-team/ros4debian | ros4debian ]] to have an almost complete installation.

Or, simply, build the [[ http://wiki.ros.org/noetic/Installation/Source | sources ]] of what you need

Shortcuts about ROS in Debian

Introduction

Robot Operating System (ROS or ros) is an open-source robotics middleware suite. Although ROS is not an operating system but a collection of software frameworks for robot software development, it provides services designed for a heterogeneous computer cluster such as hardware abstraction, low-level device control, implementation of commonly used functionality, message-passing between processes, and package management ?Wikipedia. ROS has two main versions: ROS1 and ROS2.

ROS is released as distributions, also called “distros”, with more than one ROS distribution supported at a time. Check upstream web for more information. This framework consists of about 1600 packages or projects that give a myriad of benefits for those of us who work in the field of robotics.

ROS1 installation

The official ROS page shows that the platforms supported are:

  • Ubuntu Focal amd64 armhf arm64
  • Debian Buster amd64 arm64

The rest of the platforms are experimental. In case you are running Bullseye or Testing/Unstable you cannot use Upstream packages.

The packages they provide are self-generated and do not feet most the rules of the Debian project. Each package, for example, contains a package.xml file that among other things, it contains what its dependencies are for, to build and to run the package. Upstream provides a tool python3-bloom , that it is in the archive which generates a debian directory with necessary files to run debuild from that debian directory. It's a rudimentary package that for example, provides the *.pyc files!!.

There are another options?

Yes!! A big yes. The answer depend on the number of packages that you need of ROS1. For the majority of the users, that only needs the core libraries and some applications you can use your Debian distro without any other stuff. The necessary packages are the Debian native packages and you can obtain more information here. They began to appear in the archive since Debian Stretch.

Your versions in Stable are outdated

Yes, if you are here you know how Debian works. However, you can use Debian for Robotics packages that has backported versions of Unstable and some plus to use in Debian Stable.

But, I need ros-foo that is wonderful and it is no packaged

You have several options. For instance, if you are running Debian Buster/Bullseye/Testing/Unstable) you can use the native packages and complete the rest. Here there is an example of how to do it.

If you are running Debian Bullseye, with the Debian for Robotics packages you can use ros4debian to have an almost complete installation.

Or, simply, build the sources of what you need