Hi. I uploaded a small update of this package to experimental to reduce the Build-Depends list a bit (it still builds). One of the build dependencies were 'libssl-dev'. Does anyone have any idea if that is needed for some strange reason that isn't obvious? I assume that if a pure golang-*-dev package still builds after reducing build dependencies, having that build dependency present couldn't influence anything (unless there is some magic in debian/rules but I don't see any here). Running the self-tests could be affected, but they look complete and successful here, from what I can tell. I also think that we have a large undiagnosed challenge in the Debian Go packaging ecosystem: unnecessary build dependencies. We all add Build-Depends when needed, but there are no integrated tools around to help is remove them when upstream loses them. When doing a new upstream import, I've taken the habbit of doing: dh-make-golang check-depends > ../foo gbp import-orig --uscan dh-make-golang check-depends > ../bar diff -ur ../foo ../bar And adjusting B-D's based on the diff. But I think even studying the output of 'dh-make-golang check-depends' is useful, but it is a manual and tedious process. And sometimes (especially for binaries) a build dependency may be optional and lack of it will not lead to a build failure, but some unwanted operational difference. Thoughts? /Simon
Attachment:
signature.asc
Description: PGP signature