On Wed 18 Mar 2026 at 15:35:03 +0100, Hauke Fath wrote:
> Out of interest (assume no clue about the Golang eco-system): When a
> handful of Go modules out of a hundred fail to - well, "build"?
> "integrate"?, and the error message ("undefined") points to a line in
> what looks like an interface list, what is the next step? Pester
> upstream about a platform they don't care about? Or find the respective
> module's upstream?
I would go to the upstream of the package and point out that if they
avoid all packaging systems (which golang does), they don't profit from
the porting and fixing work that the packaging systems do. Therefore it
becomes their responsibility instead to do that work. They will have to
fix the build if there is a problem. For *all* their recursive
dependencies. For *all* platforms.
Somehow people never seem to like me when I say that.
-Olaf.
--
___ Olaf 'Rhialto' Seibert <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work. --I. Rose
Attachment:
signature.asc
Description: PGP signature