Package: src:deb-build-artifact-gather Version: 0.1 People on #debian-reproducible pointed me to this package ...
Some questions: - the docs/*.md files should be part of the binary package. - it is unclear for me, how artifacts of successful and unsuccessful builds are collected, and if there is a difference - how are artifacts collected that are not part of the package builds, like preprocessed source of compiler errors, or dump files for OpenJDK crashes? These two use cases showing up as /tmp/cc* and /tmp/hs_* - X-Build-Time-Aux-Artifacts lines: Are these optional, e.g. ignored when there are no matches? Architecture specific logs should be considered. - X-Build-Time-Aux-Artifacts: what's the equivalent for find -name '*.log'? or do these have to be specified separately? - X-Build-Time-Aux-Artifacts: are there exclusion patterns for logs? - X-Build-Time-Aux-Artifacts: Are complete directory names allowed as an artifact? Use-case is getting the complete failing test in a testsuite - I assume that debhelper's config.log dumping will be replaced by this, or at least that config.log files will appear in the artifacts. test-summary.log files are currently not dumped (autotools specific?). How are these added to the artifacts without having every package maintainer specifying these themself?
