Quoting Vagrant Cascadian (2023-04-18 00:33:58) > > Do you have other short suggestions? Do we want to show it has been built > > on a debian buildd? In that case /build/debian-buildd might do it. > > Well, then a verification build using reproducible builds will be > "lying" that it is built on a buildd. :)
I don't think it would be lying. It would be saying: "I'm trying to verify something that was built on a buildd by reproducing its environment." > Or just go with "reproducible-path" as it is not tragically long if it seems > unlikely to match inappropriately. :) > > Is sbuild replacing the string mandatory; could we do without that feature? > What would we loose? Might require patching sbuild... It is not madatory. Log filtering can be switched off via the LOG_FILTER configuration option. I think the main purpose for the log filtering is to make log files easily grep-able despite the build path having random components. But if that is the only reason, then with a fixed build path log filtering is not required anymore, as anybody interested could just grep for /build/0ad-0.0.26-3_i386 and be done. Dropping log filtering would also make build logs not "lie" anymore and output stuff like: make[1]: Leaving directory '/<<PKGBUILDDIR>>' But instead output the truth: make[1]: Leaving directory '/build/0ad-0.0.26-3_i386' So maybe fixed build paths combined with disabled log filtering can actually improve the readability of log files? Thanks! cheers, josch
signature.asc
Description: signature
