Hi! On Tue, 2026-06-02 at 01:21:44 +0530, Nilesh Patra wrote: > On 01/06/26 4:49 pm, Santiago Vila wrote: > > On Sun, May 31, 2026 at 06:22:04PM +0530, Nilesh Patra wrote: > > > >> Similar to this, why can't we have go tooling add `_build/` to > >> `debian/clean` instead > >> of changing the builddir? > > > > Or just go tooling remove _build without having to add it to debian/clean. > > > > After all, python tooling (dh-python) also removes several common > > build directories in python packages (example recently added: .pdm-build), > > so we could follow a similar spirit here. > > Right. It removes `.pybuild/` too - for as long as I can remember - many > years or > such. I agree that it'd be good for go tooling to just cleanup `_build/`.
The dh-golang buildsystem (when used) already cleans whatever has been specified as --builddirectory on the «debian/rules clean» target. The same with debhelper removing any of the files that it (or dpkg) has autogenerated. This is not the problem at hand though. The problem is that if you do the equivalent of something like: $ debcheckout -a golang-foo $ cd golang-foo $ dpkg-buildpackage --build=binary $ git status That shows lots of untracked files, which can easily end up being committed into git by say «git add -A», and are in general distracting. Thanks, Guillem
