jperkin, 6 months ago

I've always tried to ship the most robust #pkgsrc packages I possibly can, with a whole suite of checks to avoid releasing packages that link against unregistered libraries.

So I was pretty embarrassed when @Neirac discovered our nodejs packages were somehow not depending on libiconv correctly.

Turns out to be a pretty thorny problem, which I've tried to summarise here:

http://mail-index.netbsd.org/tech-pkg/2023/11/24/msg028516.html

For now I've enhanced the checks in our fork, and tightened up our GCC specs. Still more to do.