Re: libssl in golang-github-google-certificate-transparency

2025-08-21 Thread Simon Josefsson
Otto Kekäläinen writes: > Good point! It is easy to add missing dependencies, but there is no tooling > to spot and remove unnecessary dependencies (and not just in Go but all of > Debian). > > I occasionally read the go.mod diff on upstream important to see what > changed, but it is all manual.

Re: libssl in golang-github-google-certificate-transparency

2025-08-21 Thread Otto Kekäläinen
> I wonder if we could make something automatic and put that into a > Go-specific Salsa CI check? I haven't given much thought to this tool or the ptrace details or other alternatives to implement this, so I can't contribute much right now in brainstorming how this should be made, but I can briefl

Re: libssl in golang-github-google-certificate-transparency

2025-08-21 Thread Otto Kekäläinen
Good point! It is easy to add missing dependencies, but there is no tooling to spot and remove unnecessary dependencies (and not just in Go but all of Debian). I occasionally read the go.mod diff on upstream important to see what changed, but it is all manual. It would be cool if the dh-golang ha

libssl in golang-github-google-certificate-transparency

2025-08-21 Thread Simon Josefsson
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 p