On 18/08/2018 11:03, Niels Thykier wrote: > Clément Hermann: >> How are we supposed to do this properly ? Not checking the compat level >> and behaving accordingly, this is documented, but the communication >> part: should we file a bug against debhelper too ? >> >> Or should we just add the switch in the code and document it in >> dh-golang, without coordinating with debhelper itself ? >> >> Thanks for any insights! >> >> Cheers, >> > > This is a very good question. I think you should definitely document it > in dh-golang itself (its manpage, etc.) regardless of whether it is > documented in debhelper.
Of course. The change is documented in dh-golang itself. Or rather it will be, because using debhelper compat level to decide what is the default behaviour is an afterthought. > Having thought about, I think I am open to having an item or two for > third-party debhelper tooling in the compatibility notes. I may have to > revise that if I start getting a lot of third-party notes but I am not > getting a lot of them. > > Could you please file a bug or merge request on salsa against debhelper > with the proposed text? I will, as soon as it is fully implemented and has been tested a bit more: it might need a few weeks before I have time to finalize this. Thanks, -- nodens
