On 14 Jun 2026, at 17:13, Mark Millard <[email protected]> wrote: > I would claim that the above effectively means that the responsibility > for indirect dependencies essentially needs to be split across the > automated build process and the automated installation process and, at > the scale involved, cannot reasonably/generally be handled at the source > code stage for tracking the indirect dependencies.
Hi, I totally agree, this is why I think that (again: unless you *directly* use stuff from some sub-dependency, and then it’s not an indirect dependency, it’s a direct one) you should not manually insert sub-dependencies in the port you maintain. It’s already quite complex this way (especially when things like python which has "it’s own dependency layer”, or dbus which depends on it just for a small compile-time component get in…), handling indirect dependencies in each port would be unaffordable IMHO. But, as correctly said, let’s wait for the final statement from who knows more. A.
