Hi, On 2023-04-16 15:16, Vagrant Cascadian wrote: > On 2023-04-16, Aurelien Jarno wrote: > > I have tried adding a simple .sbuildrc defining $build_path to '/build' > > to zandonai.d.o. Unfortunately while it more or less does what you want > > for the build path, it completely clutter the logs, as any text matching > > "build" is now replaced by "<<BUILDDIR>>": > > > > https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring&arch=s390x&ver=42.1-1%2Bb2&stamp=1681671508&raw=0 > > > > > I guess one option is to use a build path unlikely to match any string > > from a build log, like with the randomized directory. Something like > > "/build/reproducible-path/"? > > Just for clarity, then the the PKGBUILDIR would end up being > /build/reproducible-path/PACKAGE-VERSION ? That works! Or something even > shorter ... e.g. /build/path/PACKAGE-VERSION or > /build/debian/PACKAGE-VERSION ? Really, the 2nd directory matters > little, as long as it is predictible. :)
Yes, setting $build_path to '/build/debian' indeed means that PKGBUILDDIR is /build/debian/PACKAGE-VERSION. Unfortunately the string 'build/debian' appears in a few build logs: 0ad apktool gatk-bwamem gatk-fermilite gkl grpc-java haskell-debian libsis-jhdf5-java mupdf nacl openjfx pytorch xtables-addons 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. > We have noticed various packages (for better or worse) do tend to derive > information from the top-level build directory by assuming it is > PACKAGE-VERSION; probably good to cater to that assuption. > > Anything along the above lines sounds good, really! Although once a > particular bikeshed is chosen, ideally we should commit to it for the > forseeable future! :) Yes, definitely. Cheers Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
signature.asc
Description: PGP signature
