Currently, the behavior is focused on what got pulled into the build, but it'd be equally useful for traversing the limited runtime dependency graph to determine why something got installed into a rootfs.
Right now, when you run with -R, it traverses all the runtime deps at each level, rather than only the rdeps of the rdeps. If we filter that to the latter, we could use the command to look into the install deps rather than just what's being built/packaged.
Currently, the behavior is focused on what got pulled into the build, but it'd be equally useful for traversing the limited runtime dependency graph to determine why something got installed into a rootfs.
Right now, when you run with -R, it traverses all the runtime deps at each level, rather than only the rdeps of the rdeps. If we filter that to the latter, we could use the command to look into the install deps rather than just what's being built/packaged.