Skip to content
This repository was archived by the owner on Jul 1, 2021. It is now read-only.

add package.xml for poco_vendor#15

Merged
mikaelarguedas merged 2 commits intomasterfrom
add_package.xml
Jun 6, 2018
Merged

add package.xml for poco_vendor#15
mikaelarguedas merged 2 commits intomasterfrom
add_package.xml

Conversation

@mikaelarguedas
Copy link
Copy Markdown
Member

As we have control over this repository I figured it would be better to have the package.xml leaving alongthe code rather than a patch on the release repository.

@nuclearsandwich I removed 2 dependencies that didn't appread to be necessary on my bionic machine
https://github.com/ros2-gbp/poco_vendor-release/blob/7c74e1bfa5d5596fa957817c06cca3ee3b19862c/xenial/package.xml#L14-L15
I tested it by ensuring that these 2 packages were not present and building up to the "composition" package and ran the test of "composition" successfully (couldnt test it on CI as these deps are brought in transitively by other packages like opencv or python3-dev).

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

Copy link
Copy Markdown
Member

@wjwwood wjwwood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

format 3? Otherwise lgtm.

@mikaelarguedas
Copy link
Copy Markdown
Member Author

format 3?

Oh do we have a preference for format 3 ?

I usually use format 3 only when I need format 3 features, but am totally fine changing it to format 3 if it's preferred

@wjwwood
Copy link
Copy Markdown
Member

wjwwood commented Jun 6, 2018

Dunno, I always use format 3 in ROS 2. No reason, just using the latest and greatest.

@mikaelarguedas
Copy link
Copy Markdown
Member Author

Dunno, I always use format 3 in ROS 2. No reason, just using the latest and greatest.

Fine by me 49e4ab0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants