.. _MaintainingSource:

Maintain source checkout
========================

.. contents::
   :depth: 2
   :local:

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.

Update your repository list
---------------------------

Each ROS 2 release includes a ``ros2.repos`` file that contains the list of repositories and their version for that release.


Latest ROS 2 {DISTRO_TITLE} branches
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

If you wish to checkout the latest code for ROS 2 {DISTRO_TITLE}, you can get the relevant repository list by running:

.. tabs::

  .. group-tab:: Linux

    .. code-block:: console

       $ cd ~/ros2_{DISTRO}
       $ mv -i ros2.repos ros2.repos.old
       $ wget https://raw.githubusercontent.com/ros2/ros2/{REPOS_FILE_BRANCH}/ros2.repos

  .. group-tab:: macOS

    .. code-block:: console

       $ cd ~/ros2_{DISTRO}
       $ mv -i ros2.repos ros2.repos.old
       $ wget https://raw.githubusercontent.com/ros2/ros2/{REPOS_FILE_BRANCH}/ros2.repos

  .. group-tab:: Windows

    Use a Windows command line interface:

    .. code-block:: console

       $ cd \dev\ros2_{DISTRO}
       $ curl -sk https://raw.githubusercontent.com/ros2/ros2/{REPOS_FILE_BRANCH}/ros2.repos -o ros2.repos

    Or a powershell:

    .. code-block:: console

       $ cd \dev\ros2_{DISTRO}
       $ curl https://raw.githubusercontent.com/ros2/ros2/{REPOS_FILE_BRANCH}/ros2.repos -o ros2.repos


Update your repositories
------------------------

You will notice that in the `ros2.repos <https://raw.githubusercontent.com/ros2/ros2/{REPOS_FILE_BRANCH}/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:

.. code-block:: console

   $ vcs custom --args remote update

Download the new source code
----------------------------

You should now be able to download the sources associated with the new repository list with:

.. tabs::

  .. group-tab:: Linux

    .. code-block:: console

       $ vcs import src < ros2.repos
       $ vcs pull src

  .. group-tab:: macOS

    .. code-block:: console

       $ vcs import src < ros2.repos
       $ vcs pull src

  .. group-tab:: Windows

   In a Windows command line interface:

   .. code-block:: console

       $ vcs import --input ros2.repos src
       $ vcs pull src

   Or in powershell:

   .. code-block:: console

       $ vcs import --input ros2.repos src
       $ vcs pull src

Rebuild your workspace
----------------------

Now that the workspace is up to date with the latest sources, remove your previous install and rebuild your workspace with, for example:

.. code-block:: console

   $ colcon build --symlink-install

Inspect your source checkout
----------------------------

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:

.. tabs::

  .. group-tab:: Linux

    .. code-block:: console

       $ cd ~/ros2_{DISTRO}
       $ vcs export src > my_ros2.repos

  .. group-tab:: macOS

    .. code-block:: console

       $ cd ~/ros2_{DISTRO}
       $ vcs export src > my_ros2.repos

  .. group-tab:: Windows

    .. code-block:: console

       $ cd \dev\ros2_{DISTRO}
       $ vcs export src > my_ros2.repos

This ``my_ros2.repos`` file can then be shared with others so that they can reproduce the state of the repositories in your workspace.