bitter-ability-32190
09/06/2022, 5:15 PMruntime_deps
v buildtime_deps
as a longer-term strategy thoughwitty-crayon-22786
09/06/2022, 6:27 PMA change we might be able to make today is to have our dependency walker stop when hitting a packageable artifact.
Or something along those lines 🤔yea, that would be possible. it depends on having an API to filter dependencies (by type, etc) while computing
TransitiveTargets
I think packageables needsyea, possibly. API question of whether that’s: 1. easier for users to understand 2. easy to implement you’d request avruntime_deps
as a longer-term strategy thoughbuildtime_deps
TransitiveTargets
class filtered to a particular Dependencies
field typeproud-dentist-22844
09/06/2022, 7:43 PMdistcc
for distributed package builds. So, that’s something else that might be interesting prior art.
So, Gentoo has these kinds of deps:
https://devmanual.gentoo.org/general-concepts/dependencies/#dependency-types
• BDEPEND
(Build Dependencies) is for dependencies that are needed on the build host (aka CBUILD host)
• DEPEND
(also for Build Dependencies) is for dependencies on libraries/headers that are needed on the target host (aka CHOST - the machine that runs the built package)
• RDEPEND
(Runtime Dependencies) is for dependencies required at runtime like dynamically linked libs, data packages, and the relevant runtime interpreter (if applicable).
• PDEPEND
(Post Dependencies) is for runtime dependencies that can be satisfied after the package is installed - used to resolve circular dependencies.