From ee49bf691ee30be6621976fe1da52794659a94c3 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Tue, 8 Aug 2023 13:49:52 -0700 Subject: [PATCH 01/15] Add UpstreamPackages to docs.ros.org documentation Copying from: http://wiki.ros.org/UpstreamPackages --- .../Contributing/Developer-Guide.rst | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 329fec5dfb..289cbf89c3 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -470,6 +470,39 @@ Repository layout Each package should be in a subfolder which has the same name as the package. If a repository contains only a single package it can optionally be in the root of the repository. +Upstream Packages +^^^^^^^^^^^^^^^^^ + +Packages in Debian and Ubuntu Upstream +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, there are now ROS packages available upstream in Debian unstable and Ubuntu Xenial that can be installed from the main Debian and Ubuntu repositories. +`Here is a short overview from Jochen at ROSCon 2015 `_. + +Most of the packages up to desktop-full are available (`overview of package status at Debian Science `_). The original ROS packages have been modified to follow Debian guidelines, which includes splitting packages into multiple pieces, changing names in some cases, installing to /usr according to FHS guidelines, and using soversions on shared libraries. For example, roslib is called python-roslib and roscpp is in the libroscpp-dev and libroscpp0d packages. + +Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific `ROS distribution `_. +Rather, they represent a rolling release that will be updated periodically within Debian unstable and then periodically latched at various points into downstream Debian and Ubuntu distributions. + +Don't mix the streams +~~~~~~~~~~~~~~~~~~~~~ +We strongly recommend against mixing ROS packages from upstream Debian/Ubuntu and from packages.ros.org on the same system. +In some cases such a mixed system will work correctly, but there can be negative interactions between the two sets of packages. +We’re working with Jochen and friends to minimize the chance of problems via documentation and package conflict specifications, but we expect some risks to remain, including some fairly subtle issues. + +As such, we recommend that you choose to either install packages from upstream or from packages.ros.org, but not both. +Not only should you not install packages from both at the same time, but if you intend to use the upstream packages (not from packages.ros.org) then you should not even have the packages.ros.org entries in your apt sources (i.e. in any files in /etc/apt/sources*) as this can cause mixing of packages which overlap by name between the two sources, e.g. python-rospkg. + +Known Differences +~~~~~~~~~~~~~~~~~ +As compared to the ROS packages from packages.ros.org, there are some differences in the upstream ROS packages that people should be aware of: + +* The package set is incomplete. + Unsurprisingly, not all packages are yet available upstream. Currently the packages of desktop-full are available and we anticipate that more will become available over time. +* Packages may have different names and be partitioned differently. + + + Developer Workflow ------------------ From 5940ab80d057f366f790f41ae95760c67d59eb5a Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Wed, 13 Sep 2023 21:30:50 +0000 Subject: [PATCH 02/15] Updates from review feedback --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 289cbf89c3..22d63fcf96 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -479,9 +479,12 @@ Packages in Debian and Ubuntu Upstream Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, there are now ROS packages available upstream in Debian unstable and Ubuntu Xenial that can be installed from the main Debian and Ubuntu repositories. `Here is a short overview from Jochen at ROSCon 2015 `_. -Most of the packages up to desktop-full are available (`overview of package status at Debian Science `_). The original ROS packages have been modified to follow Debian guidelines, which includes splitting packages into multiple pieces, changing names in some cases, installing to /usr according to FHS guidelines, and using soversions on shared libraries. For example, roslib is called python-roslib and roscpp is in the libroscpp-dev and libroscpp0d packages. +Most of the ROS 1 packages up to desktop-full are available (`overview of package status at Debian Science `_). +The original ROS packages have been modified to follow Debian guidelines, which includes splitting packages into multiple pieces, changing names in some cases, installing to /usr according to FHS guidelines, and using soversions on shared libraries. +For example, roslib is called python-roslib and roscpp is in the libroscpp-dev and libroscpp0d packages. +In addition several of the bootstrap dependencies such as command line tools like `vcstool` and `colcon` as well as some libraries like `osrf-pycommon` and `ament` are also packaged upstream. -Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific `ROS distribution `_. +Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific `ROS distribution `_. Rather, they represent a rolling release that will be updated periodically within Debian unstable and then periodically latched at various points into downstream Debian and Ubuntu distributions. Don't mix the streams @@ -501,8 +504,6 @@ As compared to the ROS packages from packages.ros.org, there are some difference Unsurprisingly, not all packages are yet available upstream. Currently the packages of desktop-full are available and we anticipate that more will become available over time. * Packages may have different names and be partitioned differently. - - Developer Workflow ------------------ From 52770c899e16bd509b9043de19c50fbb26b5fe8c Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Thu, 14 Sep 2023 10:07:05 -0700 Subject: [PATCH 03/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 22d63fcf96..fc73bebd3c 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -476,12 +476,10 @@ Upstream Packages Packages in Debian and Ubuntu Upstream ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, there are now ROS packages available upstream in Debian unstable and Ubuntu Xenial that can be installed from the main Debian and Ubuntu repositories. -`Here is a short overview from Jochen at ROSCon 2015 `_. - -Most of the ROS 1 packages up to desktop-full are available (`overview of package status at Debian Science `_). +Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, some of the ROS 2 packages are now available from the main Debian and Ubuntu repositories. +`Here is a short overview of the process from Jochen at ROSCon 2015 `_. The original ROS packages have been modified to follow Debian guidelines, which includes splitting packages into multiple pieces, changing names in some cases, installing to /usr according to FHS guidelines, and using soversions on shared libraries. -For example, roslib is called python-roslib and roscpp is in the libroscpp-dev and libroscpp0d packages. + In addition several of the bootstrap dependencies such as command line tools like `vcstool` and `colcon` as well as some libraries like `osrf-pycommon` and `ament` are also packaged upstream. Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific `ROS distribution `_. From 275a3659ab724089e71b835488a8f4eddba858ea Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Thu, 14 Sep 2023 10:07:40 -0700 Subject: [PATCH 04/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index fc73bebd3c..894444e182 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -482,7 +482,7 @@ The original ROS packages have been modified to follow Debian guidelines, which In addition several of the bootstrap dependencies such as command line tools like `vcstool` and `colcon` as well as some libraries like `osrf-pycommon` and `ament` are also packaged upstream. -Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific `ROS distribution `_. +Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`_. Rather, they represent a rolling release that will be updated periodically within Debian unstable and then periodically latched at various points into downstream Debian and Ubuntu distributions. Don't mix the streams From 3bd6ecdfec5d3e5d5f776439b73432701a9e4f31 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Thu, 14 Sep 2023 10:07:55 -0700 Subject: [PATCH 05/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 894444e182..b8278b3ccd 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -492,7 +492,8 @@ In some cases such a mixed system will work correctly, but there can be negative We’re working with Jochen and friends to minimize the chance of problems via documentation and package conflict specifications, but we expect some risks to remain, including some fairly subtle issues. As such, we recommend that you choose to either install packages from upstream or from packages.ros.org, but not both. -Not only should you not install packages from both at the same time, but if you intend to use the upstream packages (not from packages.ros.org) then you should not even have the packages.ros.org entries in your apt sources (i.e. in any files in /etc/apt/sources*) as this can cause mixing of packages which overlap by name between the two sources, e.g. python-rospkg. +Not only should you not install packages from both at the same time, but if you intend to use the upstream packages (not from packages.ros.org) then you should not even have the packages.ros.org entries in your apt sources (i.e. in any files in ``/etc/apt/sources*``). +Having both of them enabled can cause mixing of packages which overlap by name between the two sources, e.g. ``python3-rospkg``. Known Differences ~~~~~~~~~~~~~~~~~ From 687afbd773757be6e86a31f52f377fc76fcd49df Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Thu, 14 Sep 2023 10:08:11 -0700 Subject: [PATCH 06/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index b8278b3ccd..80df483ba7 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -500,7 +500,6 @@ Known Differences As compared to the ROS packages from packages.ros.org, there are some differences in the upstream ROS packages that people should be aware of: * The package set is incomplete. - Unsurprisingly, not all packages are yet available upstream. Currently the packages of desktop-full are available and we anticipate that more will become available over time. * Packages may have different names and be partitioned differently. Developer Workflow From 62807d28042fc521e6ce32b8c5ce8acac6ba00e9 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Thu, 14 Sep 2023 10:09:09 -0700 Subject: [PATCH 07/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 80df483ba7..969cacece2 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -483,7 +483,7 @@ The original ROS packages have been modified to follow Debian guidelines, which In addition several of the bootstrap dependencies such as command line tools like `vcstool` and `colcon` as well as some libraries like `osrf-pycommon` and `ament` are also packaged upstream. Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`_. -Rather, they represent a rolling release that will be updated periodically within Debian unstable and then periodically latched at various points into downstream Debian and Ubuntu distributions. +Rather, they represent a snapshot in time that will be updated periodically within Debian unstable and then latched at various points into downstream Debian and Ubuntu distributions. Don't mix the streams ~~~~~~~~~~~~~~~~~~~~~ From 9b926519cd881759a37e0698d8e94a654f2f5bdd Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Thu, 14 Sep 2023 10:18:00 -0700 Subject: [PATCH 08/15] fix link formatting --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 969cacece2..a93bf2544c 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -482,7 +482,7 @@ The original ROS packages have been modified to follow Debian guidelines, which In addition several of the bootstrap dependencies such as command line tools like `vcstool` and `colcon` as well as some libraries like `osrf-pycommon` and `ament` are also packaged upstream. -Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`_. +Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`. Rather, they represent a snapshot in time that will be updated periodically within Debian unstable and then latched at various points into downstream Debian and Ubuntu distributions. Don't mix the streams From 3bfbcd11b4fb8bccd9a0b6b56c7850f5697fb891 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Mon, 25 Sep 2023 17:24:28 -0700 Subject: [PATCH 09/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index a93bf2544c..87027f7e6b 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -480,7 +480,7 @@ Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, `Here is a short overview of the process from Jochen at ROSCon 2015 `_. The original ROS packages have been modified to follow Debian guidelines, which includes splitting packages into multiple pieces, changing names in some cases, installing to /usr according to FHS guidelines, and using soversions on shared libraries. -In addition several of the bootstrap dependencies such as command line tools like `vcstool` and `colcon` as well as some libraries like `osrf-pycommon` and `ament` are also packaged upstream. +In addition several of the bootstrap dependencies such as command line tools like ``vcstool`` and ``colcon`` as well as some libraries like ``osrf-pycommon`` and ``ament`` are also packaged upstream. Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`. Rather, they represent a snapshot in time that will be updated periodically within Debian unstable and then latched at various points into downstream Debian and Ubuntu distributions. From 97132127595c66f286d24d78b4b77d377a0b146f Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Mon, 25 Sep 2023 17:25:03 -0700 Subject: [PATCH 10/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 87027f7e6b..d24196fc70 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -487,7 +487,7 @@ Rather, they represent a snapshot in time that will be updated periodically wit Don't mix the streams ~~~~~~~~~~~~~~~~~~~~~ -We strongly recommend against mixing ROS packages from upstream Debian/Ubuntu and from packages.ros.org on the same system. +We strongly recommend against mixing ROS packages from upstream Debian/Ubuntu and from http://packages.ros.org on the same system. In some cases such a mixed system will work correctly, but there can be negative interactions between the two sets of packages. We’re working with Jochen and friends to minimize the chance of problems via documentation and package conflict specifications, but we expect some risks to remain, including some fairly subtle issues. From 540b9f4763d8ece120c7228589e7cbd3e6ec55c3 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Mon, 25 Sep 2023 17:25:30 -0700 Subject: [PATCH 11/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index d24196fc70..929370bd11 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -492,7 +492,7 @@ In some cases such a mixed system will work correctly, but there can be negative We’re working with Jochen and friends to minimize the chance of problems via documentation and package conflict specifications, but we expect some risks to remain, including some fairly subtle issues. As such, we recommend that you choose to either install packages from upstream or from packages.ros.org, but not both. -Not only should you not install packages from both at the same time, but if you intend to use the upstream packages (not from packages.ros.org) then you should not even have the packages.ros.org entries in your apt sources (i.e. in any files in ``/etc/apt/sources*``). +Not only should you not install packages from both at the same time, but if you intend to use the upstream packages then you should not even have the http://packages.ros.org entries in your apt sources (i.e. in any files in ``/etc/apt/sources*``). Having both of them enabled can cause mixing of packages which overlap by name between the two sources, e.g. ``python3-rospkg``. Known Differences From 64dbba35bc21b36d1c2466f03770c328d61870c2 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Mon, 25 Sep 2023 17:25:45 -0700 Subject: [PATCH 12/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 929370bd11..29da71a004 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -491,7 +491,7 @@ We strongly recommend against mixing ROS packages from upstream Debian/Ubuntu an In some cases such a mixed system will work correctly, but there can be negative interactions between the two sets of packages. We’re working with Jochen and friends to minimize the chance of problems via documentation and package conflict specifications, but we expect some risks to remain, including some fairly subtle issues. -As such, we recommend that you choose to either install packages from upstream or from packages.ros.org, but not both. +As such, we recommend that you choose to either install packages from upstream or from http://packages.ros.org, but not both. Not only should you not install packages from both at the same time, but if you intend to use the upstream packages then you should not even have the http://packages.ros.org entries in your apt sources (i.e. in any files in ``/etc/apt/sources*``). Having both of them enabled can cause mixing of packages which overlap by name between the two sources, e.g. ``python3-rospkg``. From 2e62c9549e65fc3b686f462fc8d8f7bf42ca10ea Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Mon, 25 Sep 2023 17:31:28 -0700 Subject: [PATCH 13/15] Add link to ROS 2 packages --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 29da71a004..89c8491dba 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -476,7 +476,7 @@ Upstream Packages Packages in Debian and Ubuntu Upstream ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, some of the ROS 2 packages are now available from the main Debian and Ubuntu repositories. +Thanks to diligent effort from Jochen Sprickerhof and Leopold Palomo-Avellaneda, some of the `ROS 2 packages are now available `_ from the main Debian and Ubuntu repositories. `Here is a short overview of the process from Jochen at ROSCon 2015 `_. The original ROS packages have been modified to follow Debian guidelines, which includes splitting packages into multiple pieces, changing names in some cases, installing to /usr according to FHS guidelines, and using soversions on shared libraries. From 64aab0bc5a090be366f28e35619b430d9016e7e5 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Mon, 25 Sep 2023 17:33:46 -0700 Subject: [PATCH 14/15] Update source/The-ROS2-Project/Contributing/Developer-Guide.rst Co-authored-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 89c8491dba..2e823a7fa3 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -482,7 +482,7 @@ The original ROS packages have been modified to follow Debian guidelines, which In addition several of the bootstrap dependencies such as command line tools like ``vcstool`` and ``colcon`` as well as some libraries like ``osrf-pycommon`` and ``ament`` are also packaged upstream. -Unlike the OSRF-provided ROS packages from packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`. +Unlike the OSRF-provided ROS packages from http://packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`. Rather, they represent a snapshot in time that will be updated periodically within Debian unstable and then latched at various points into downstream Debian and Ubuntu distributions. Don't mix the streams From d483a1fecc08571bd8b471a8a27eea17840e471f Mon Sep 17 00:00:00 2001 From: Chris Lalancette Date: Tue, 26 Sep 2023 08:39:09 -0400 Subject: [PATCH 15/15] Minor formatting fixes. Signed-off-by: Chris Lalancette --- source/The-ROS2-Project/Contributing/Developer-Guide.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst index 2e823a7fa3..abf89eb487 100644 --- a/source/The-ROS2-Project/Contributing/Developer-Guide.rst +++ b/source/The-ROS2-Project/Contributing/Developer-Guide.rst @@ -483,10 +483,11 @@ The original ROS packages have been modified to follow Debian guidelines, which In addition several of the bootstrap dependencies such as command line tools like ``vcstool`` and ``colcon`` as well as some libraries like ``osrf-pycommon`` and ``ament`` are also packaged upstream. Unlike the OSRF-provided ROS packages from http://packages.ros.org, the packages in the upstream repositories are not attached to a specific :doc:`ROS distribution <../../Releases>`. -Rather, they represent a snapshot in time that will be updated periodically within Debian unstable and then latched at various points into downstream Debian and Ubuntu distributions. +Rather, they represent a snapshot in time that will be updated periodically within Debian unstable and then latched at various points into downstream Debian and Ubuntu distributions. Don't mix the streams ~~~~~~~~~~~~~~~~~~~~~ + We strongly recommend against mixing ROS packages from upstream Debian/Ubuntu and from http://packages.ros.org on the same system. In some cases such a mixed system will work correctly, but there can be negative interactions between the two sets of packages. We’re working with Jochen and friends to minimize the chance of problems via documentation and package conflict specifications, but we expect some risks to remain, including some fairly subtle issues. @@ -497,6 +498,7 @@ Having both of them enabled can cause mixing of packages which overlap by name b Known Differences ~~~~~~~~~~~~~~~~~ + As compared to the ROS packages from packages.ros.org, there are some differences in the upstream ROS packages that people should be aware of: * The package set is incomplete.