Re: Put artifacts in `debian/_build` by default instead of `_build` - please review open team MRs and PRs

[Ananthu C V]

On 31 May 2026 12:52:04 UTC, Nilesh Patra <nil...@debian.org> wrote:
>I somehow don't understand how this is even specific to golang packages. I 
>have seen
>quite some C library packages which (using cmake mostly) output stuff into
>obj-<arch__triplet> directory in the root itself; and adding that to 
>`debian/clean`
>is often the right thing to do.
>
>Similar to this, why can't we have go tooling add `_build/` to `debian/clean` 
>instead
>of changing the builddir?
>

Thanks, this is exactly what I was thinking after seeing this proposal. I don't 
have a strong opinion on putting the builddir inside or outside debian/ dir, 
but either way we have to clean it ultimately. debian/.gitignore to my 
understanding is a terrible way of dealing with leftover build artifacts. So 
regardless of where we put the build dir, as long as the tooling cleans it 
properly there would be no issues.
-- 
Best,
Ananthu