Add ros2 pkg depends verb - #1268
Conversation
Signed-off-by: Miko Parkkinen <141511110+Miko997@users.noreply.github.com>
|
Tick the box to add this pull request to the merge queue (same as
|
fujitatomoya
left a comment
There was a problem hiding this comment.
what is the difference between this and ros2 pkg xml | grep? for maintainability, we do not want to maintain the overlapped features for sure.
besides, #44 is originally created almost 10 years ago. i am not sure if there are any requests from community... at least, it's been 10 years...
|
Would the outcome be different than ? |
|
@Miko997 a couple of questions here before starting review, please have them checked out. |
|
The outcome is different. This verb reads an installed package from the ament index and prints its unique direct dependencies after evaluating conditions. It does not require a source workspace or colcon. I have not found newer demand beyond #44. If that installed-package use case does not justify another verb, I am happy to close the PR. |
|
Thanks for the clarification! |
Description
Add
ros2 pkg depends <package_name>to print the package's direct declared dependencies.The verb reads the installed
package.xml, evaluates dependency conditions against the current environment, and prints unique dependency names in sorted order. Recursive lookup and dependency-type filters are outside this PR.Addresses #44
Is this user-facing behavior change?
Yes.
ros2 pkgnow provides adependsverb for installed packages.Additional Information
Validation:
ros2pkgtests excluding unavailablexmllint: 6 passed, 1 deselectedgit diff --checkxmllintwas not available in the test environment. This PR does not change XML files.