+1 I've been manually reverting the .gitignore commit when I remember it, but it is really tedious and time consuming, and I agree dh-make-golang should not be modifying non-debian/ files automatically. Btw, I have several C packages that also use --builddirectory=build. Is there a simple explanation of what the advantage is to move --builddirectory to debian/build? I agree it looks better, so I'm +1 on it, but it also doesn't strike me as a critical problem, unless I'm missing something? Build systems often polute the source directory during builds, and I haven't seen any serious fallout due to this? Is the argument that this is to allow making the source directory immutable and read-only, and only have debian/ writeable? I wonder how many packages would break if that were to be tested. /Simon Otto Kekäläinen <otto@debian.org> writes: > Hi! > > Is the Go team in Debian ready to do these changes for new packages? > 1. Stop modifying upstream /.gitignore and use /debian/.gitignore > instead if needed > 2. Stop putting build artifacts in /_build for new packages and use > /debian/_build instead) > > I have been proposing this since 2024 [1] and again in 2025 [2] and > feel we really need to get this done now that the new debaudit service > will potentially start flagging packages that do modifications outside > the debian/ subdirectory, as Debian packages are not supposed to do > that (other than via proper patch). > > If you agree, please vote by doing +1 or Approve on > https://github.com/Debian/dh-make-golang/pull/248 > > [1] https://lists.debian.org/debian-go/2024/12/msg00021.html > [2] https://lists.debian.org/debian-go/2025/01/msg00005.html >
Attachment:
signature.asc
Description: PGP signature