On Thu, 15 Feb 2024 15:09:01 +0100, Joel Sing wrote: > > The operating system specific parts of the Go syscall package are effectively > deprecated/frozen (and have been for nearly 10 years, hence not being > updated): > > https://pkg.go.dev/syscall > > > https://go.googlesource.com/proposal/+/refs/heads/master/design/freeze-syscall.md > > On the other hand, golang.org/x/sys/unix is maintained and updated > semi-regularly: > > https://pkg.go.dev/golang.org/x/sys/unix > > With the exception of the OpenBSD syscall numbers: > > > https://cs.opensource.google/go/x/sys/+/master:unix/zsysnum_openbsd_amd64.go;l=8 >
Anyway, some systems are rebuild qutie often. For example Solaris [1] or FreeBSD [2]. And current state of syscall numbers for OpenBSD misses a lot [3]. Here my point: it is deprected, but still in use for some large applications like Docker, and we have two options here: (1) update it / fix it in Go, (2) patch each application by replacing Syscall.EBADMSG for example [4]. From my point of view move by (1) seems the simpler way which allows to reduce number of hacks / patches in ports. Footnotes: [1] https://github.com/golang/go/commit/ea14b633627f467a2e35eb7f67df6f3ed60469c0 [2] https://go-review.googlesource.com/c/go/+/563835 [3] https://github.com/catap/go/commit/c9cb73913d79e490f167ff1c0a651d69c700f02a [4] https://github.com/search?q=repo%3Aopenbsd%2Fports%20EBADMSG&type=code -- wbr, Kirill
