Hi Tong,
> Seems that the fix only checks the package name, not build-depends,
> while I'm building a binary out of go source, not go lib, thus my
> package name doesn't have golang- prefix
This is a good summary of the situation; if Lintian only has
visibility against the binary, it cannot (currently) identify it as
being a Go project and thus skip this tag.
Can you suggest a more reliable way to detect Go binary packages? I
spot that golang is listed in the Built-Using field; could this work
instead of just the name?
(Not a Go developer...)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] 🍥 chris-lamb.co.uk
`-
