Daniel Baumann <[email protected]> writes: > On 9/1/26 11:10, Simon Josefsson wrote: >> 3) The solution for Debian packaging of Go projects is to prepare one >> Debian source package for each API version, and make consumers of that >> particular API version depend on that Debian source package. > > jftr, the last one probably should be 'Debian binary package', right?
Right, I intended to write 'depend on a binary package from that Debian source package', but it means the same in practice. >> I believe this is an acceptable trade-off for the project at large. > > I think so too; > > somewhat related - while it's not technically needed but very > convenient for various QA things, has someone already identified how > many and which packages are declaring a go import path but have either > the source package or the binary package named "wrongly"? should we > have a lintian warning for that? > > For this and other QA things, did someone already set up a regular > check for that with a html output or so? I think a lintian check for go.mod vs debian/control naming was recently added. But maybe more checks would be useful too. There are several things that could be consistent, which we currently do not check. /Simon
signature.asc
Description: PGP signature
