ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

It has nothing to do with metapackages.

When releasing a repository, which contains one or more packages which may or may not be metapackages, you can create a file in the master branch which starts with the track name and has the extension .ignored. So if you are running the track hydro, then any packages (separated by whitespace) in the hydro.ignored file in the master branch will be ignored.

When being ignored a package will not have release branches or debian branches generated and it will not be included in the automatically generated diff nor the pull request.

The explicitly ignored packages will be noted in the README.md summary on the master branch of the repository.

Like this:

https://github.com/wjwwood/roscpp_core-release#roscpp_core---0315-5

It has nothing to do with metapackages.

When releasing a repository, which contains one or more packages which may or may not be metapackages, you can create a file in the master branch which starts with the track name and has the extension .ignored. So if you are running the track hydro, then any packages (separated by whitespace) in the hydro.ignored file in the master branch will be ignored.

When being ignored a package will not have release branches or debian branches generated and it will not be included in the automatically generated diff nor the pull request.

The explicitly ignored packages will be noted in the README.md summary on the master branch of the repository.

Like this:

https://github.com/wjwwood/roscpp_core-release#roscpp_core---0315-5


Edit by @130s The link to wjwwood/roscpp_core-release above no longer exists. This in ros-gbp/ros_comm-release might be another good example.