Buildroot dependency resolution 2.0

[asamalik]

Build dependencies are currently resolved in an external service (dep-tracker because every SRPM (source package) needs to be rebuilt for all architectures. That's necessary because dependencies can vary across different architectures. And unlike with RPMs (binary packages), SRPMs are not distributed per-architecture, as their primary use case is to distribute the sources rather than provide dependency information.

Because the build dependencies are resolved by an external service , the results might be lagging even several hours. There's also currently no distinction between direct build dependencies and dependencies of build dependencies in on the package details page.

So I want to figure out how to optimise this situation.

[yselkowitz]

@asamalik is this done already?

[asamalik]

Ah! Yeah that's the current buildroot resolver. Closing!