ROS 2 / JAZZY
gz_launch_vendor
Manifest version: 0.0.6 · Upstream repository ID: gz_launch_vendor
Purpose and upstream context
Topics explicitly mentioned in the upstream description: simulation · launch configuration.
What to test before changing versions
Its direct runtime dependencies span multiple upstream repositories. For an offline image, verify the relevant revisions and conditions in each repository, then reproduce the build from the same sources.
Execution (18): binutils · gz-launch7 · gz_cmake_vendor · gz_common_vendor
Runtime consumers in upstream release manifests (including unindexed packages): 0
- Upstream license declarations
- Apache License 2.0
- Build type
- ament_cmake
- Release repository version
- 0.0.6-1
Selection evidence, excluding generic scaffolding and test fixtures
- Qualifying runtime consumers
- 0
- Non-generic runtime dependencies
- 18
- Of these, released ROS dependencies
- 9
- Other repositories supplying these ROS dependencies
- 9
Direct dependency declarations
These are manifest declarations, not installed packages. A generic depend applies to build, export and execution. Evaluate conditions and version bounds in the target environment. An unindexed name can be a system dependency key.
Build and export (22)
Execution (18)
Testing (4)
Documentation (0)
No matching record in this snapshot
Group references (0)
No matching record in this snapshot
Direct dependency declarations · Not declared or not confirmed (18)
binutils· Not a released name in this snapshot; check rosdep or the source workspacelibgflags-dev· Not a released name in this snapshot; check rosdep or the source workspacelibwebsockets-dev· Not a released name in this snapshot; check rosdep or the source workspacelibxi-dev· Not a released name in this snapshot; check rosdep or the source workspacelibxmu-dev· Not a released name in this snapshot; check rosdep or the source workspacelibyaml-dev· Not a released name in this snapshot; check rosdep or the source workspacetinyxml2· Not a released name in this snapshot; check rosdep or the source workspaceuuid· Not a released name in this snapshot; check rosdep or the source workspaceament_cmake_core· Released; no detail page in this catalogament_cmake_test· Released; no detail page in this catalogament_cmake_vendor_package· Released; no detail page in this catalogcmake· Not a released name in this snapshot; check rosdep or the source workspacegz-launch7· Not a released name in this snapshot; check rosdep or the source workspacegz_cmake_vendor· Released; no detail page in this catalogament_cmake_copyright· Released; no detail page in this catalogament_cmake_lint_cmake· Released; no detail page in this catalogament_cmake_xmllint· Released; no detail page in this catalogxvfb· Not a released name in this snapshot; check rosdep or the source workspace
Conditions and version bounds (1)
gz-launch7 · depend · $GZ_BUILD_FROM_SOURCE != ''
Which packages directly depend on it?
Counts cover direct declarations in this snapshot only. They are neither install counts nor the full transitive impact.
Build and export (0)
No matching record in this snapshot
Execution (0)
No matching record in this snapshot
Testing (0)
No matching record in this snapshot
Documentation (0)
No matching record in this snapshot
Verify in your Jazzy environment
In a configured Jazzy shell, confirm the distribution and inspect the installed prefix, manifest and registered executables. Libraries and interface packages may list no executables. These commands are for local checks, not CHINZY deployment or benchmark results.
printenv ROS_DISTRO
ros2 pkg prefix gz_launch_vendor
ros2 pkg xml gz_launch_vendor
ros2 pkg executables gz_launch_vendorDownload verification checklist (CSV) ↓Jazzy distribution source
· Jazzy · 43a0316dfc39