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?
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?
My todo isn't lacking items, but.. those would be on it (without any ETA).
Regards,
Daniel
