The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
There is no version specified for each package.
There ARE versions specified. In the ament/ament_cmake example you posted, it's humble.
The "version" terminology in vcstool may be indeed a bit undocumented IINM. This field can take branch / tag of the vcs tool of your choice (e.g. git).
So in the ament/ament_cmake example again, "humble" seems to be the name of a branch on that repo, which means, yes it'll fetch the latest on that branch.
You can create your own .repos file and supply it to vcs import command by e.g.
vcs import src < ./foo/baa.repos
| | 2 | No.2 Revision |
There is no version specified for each package.
There ARE versions specified. In the ament/ament_cmake example you posted, it's humble.
The "version" terminology in vcstool may be indeed a bit undocumented IINM. This field can take branch / tag of the vcs tool of your the choice (e.g. git). ) of each repo.
So in the ament/ament_cmake example again, "humble" seems to be the name of a branch on that repo, which means, yes it'll fetch the latest on that branch.
You can create your own .repos file (to e.g. modify version fields) and supply it to vcs import command by e.g.
vcs import src < ./foo/baa.repos
| | 3 | No.3 Revision |
There is no version specified for each package.
There ARE versions specified. In the ament/ament_cmake example you posted, it's humble.
The "version" terminology in vcstool may be indeed a bit undocumented IINM. This field can take branch / tag of the vcs tool of the choice (e.g. git) of each repo.
So in the ament/ament_cmake example again, "humble" seems to be the name of a branch branch "version" on that repo, which means, yes it'll fetch the latest on that branch.
You can create your own .repos file (to e.g. modify version fields) and supply it to vcs import command by e.g.
vcs import src < ./foo/baa.repos
| | 4 | No.4 Revision |
UPDATE: As in comment section, this answer may not offer a straight-forward resolution to the OP's problem. Yet, in a hope that it gives some generic detail about vcstool's usage that may not be well documented, I keep it posted.
There is no version specified for each package.
There ARE versions specified. In the ament/ament_cmake example you posted, it's humble.
The "version" terminology in vcstool may be indeed a bit undocumented IINM. This field can take branch / tag of the vcs tool of the choice (e.g. git) of each repo.
So in the ament/ament_cmake example again, "humble" seems to be the name of a branch "version" on that repo, which means, yes it'll fetch the latest on that branch.
You can create your own .repos file (to e.g. modify version fields) and supply it to vcs import command by e.g.
vcs import src < ./foo/baa.repos
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.