Hi, Quoting Jérémy Lal (2025-02-14 22:38:42) > When the list of build-dependencies grows too much, it starts to be difficult > to check wether they are all actually needed. > > Maybe some sbuild backend can allow tracking of accessed files during build ?
https://gitlab.mister-muffin.de/josch/findunusedbd Helmut Grohne was working on a similar tool around the same time which used ptrace to create build logs with semantics: each line contains what tool it comes from and the process tree of each tool as it was called. The problem with either solution are test suites. Whichever solution is used, it will only work for a subset of packages: those which do not use mechanisms in their testsuite which breaks tracing. I am not aware of a mechanism today, more than 10 years later, which would allow to trace processes without also influencing them in a way that can break the tracing... Thanks! cheers, josch
signature.asc
Description: signature
