To ignore some pkgs upon release by bloom

asked 2013-07-03 08:04:51 -0600

10937 ●203 ●339 ●330 http://www.linkedin.co...

updated 2013-07-03 08:19:22 -0600

I just found at a comment on github there's a way to ignore certain packages when I release a ~~metapkg~~ repository How exactly is it done?

Suppose in package foo with a tag bar, create bar.ignored on the home directory of foo? And inside of bar.ignore listed are the names of packages that I don't to release like the following?:

pkg-foo-a
pkg-foo-b

Comments

was it not bar.ignored ? (instead of bar.ignore)

isucan ( 2013-07-03 08:09:09 -0600 )edit

Thanks, now corrected.

130s ( 2013-07-03 08:20:05 -0600 )edit

add a comment

answered 2013-07-03 08:09:28 -0600

William

17335 ●101 ●182 ●262 http://wjwwood.io/

updated 2016-10-20 15:04:18 -0600

130s

10937 ●203 ●339 ●330 http://www.linkedin.co...

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_cor...

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.

edit flag offensive delete link

Comments

Just to make sure, is master branch replaced (eg. with the default branch on my github repo) when no master branch exists?

130s ( 2013-07-03 08:17:58 -0600 )edit

No... this is not your upstream repository. This is the release repository. Bloom places all of its configurations on the master branch. There is no way to change this.