Maintaining a source checkout of ROS 2¶
If you have installed ROS 2 from source, there may have been changes made to the source code since the time that you checked it out.
To keep your source checkout up to date, you will have to periodically update your
ros2.repos file, download the latest sources, and rebuild your workspace.
Each ROS 2 release includes a
ros2.repos file that contains the list of repositories and their version for that release.
If you wish to update a particular release, you can get its repository list by specifying the codename of the release in the URL of the following step, e.g. foxy:
The format of the name of the release comes from the tag associated with the release here.
If you wish to checkout development branches for a particular release, you can get its repository list by specifying the codename of the release in the URL of the following step, e.g. foxy:
You will notice that in the ros2.repos file, each repository has a
version associated with it that points to a particular commit hash, tag, or branch name.
It is possible that these versions refer to new tags/branches that your local copy of the repositories will not recognize as they are out-of-date.
Because of this, you should update the repositories that you have already checked out with the following command:
vcs custom --args remote update
You should now be able to download the sources associated with the new repository list with:
Now that the workspace is up to date with the latest sources, remove your previous install and rebuild your workspace with, for example:
colcon build --symlink-install
During your development you may have deviated from the original state of your workspace from when you imported the repository list. If you wish to know the versions of the set of repositories in your workspace, you can export the information using the following command:
my_ros2.repos file can then be shared with others so that they can reproduce the state of the repositories in your workspace.