bazel-contrib/rules_distroless

`dpkg_status` does not add transitive dependencies

Open

#54 opened on May 29, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Starlark (70 forks)auto 404
feature requesthelp wanted

Repository metrics

Stars
 (97 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently there is no transitive dependency resolution of the packages that you provide to the dpkg_status rule. This causes apt to complain about missing dependencies and thinking that the install is broken. It might be possible to work around with a custom rule to resolve transitive deps of the top level packages you want to have installed before passing to dpkg_status, but it feels like this should be default behavior.

Contributor guide

Research direction
Understand how dpkg status currently resolves packages and investigate Bazel's dependency resolution mechanisms. Look into existing rules for transitive dependency handling in the Bazel ecosystem, and propose a patch to add recursive dependency resolution to the dpkg status rule.
Tech stack
None
Domain
backenddevopsinfrastructurebuild system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
BazelStarlarkLinux packaging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50