Conversation
Signed-off-by: Ian Chen <ichen@openrobotics.org>
|
cc @caguero |
|
@j-rivero checking if you're ok with this approach of trusting the repo or if we should just go with the ros2 vendor packages? If we go with the ros2 vendor packages, I only see the zenoh_cpp_vendor package but here's no |
For sure we'll need zenoh-c or zenoh-pico installed in the system. |
Ok tested with the |
Although the httpS offers some protection against possible attacks, the lack of signing packages is something to consider since there could be several issues that could make that repository vulnerable. I'll discuss with the infra group next week but let's put this on pause by now. |
|
Closing in favor of #96 until eclipse-zenoh/ci#316 is resolved. |
Related PR: gazebosim/gz-transport#600
Adds the eclipse zenoh repo to the repository.yaml config file.
From zenoh deb installation page, the instruction to add their repo is
Some notes:
trusted=yes(instead ofsigned-by=xxx.gpg).deb {url} {distribution} {component}format but it's in the form ofdeb {url} {suite}where suite in this case is just an absolute path/. So I modified the code to support this use case.Alternative considered
If we are not ok with trusting a repo without gpg signing, the alternative is to use ros2 repo's
ros-rolling-zenoh-cpp-vendorpackage for gz-transport15. The caveat is that we will need to search for a different package name in cmake, i.e.find_package(zenoh_cpp_vendor REQUIRED)