For some reason, we're stuck on a slightly older (but still supported) version of node 14/npm 6. If we try to run npm commands with the latest LTS node 16/npm 8, `npm install` fails. There's already an `.nvmrc` file in the web directory to signal which version of node is needed, but this causes the `make.bash` file to make sure that version is actually used. Does nothing if the developer does not have nvm installed, they'll just get the warning about "unsupported engine."
In addition to providing similar functionality (bundle static data into
the binary), this new package does not require us to commit the binary
blob into the repo since it is supported by the Go toolchain. No more
"forgot to run go generate after modifying the front-end code"-issues.
This changes the required Go version to >= 1.16.
Debian stable now ships with Go 1.11, and 1.11 are available for
oldstable through backports. Keeping compatibility with older versions
seems unnecessary.
Users are adviced to use the latest stable Go version.
Closes#122
On Go 1.10 the -ldflags should only apply to packages explicitly listed in the
packages list of the build command. It is probably a bug that the ldflags option
does not apply when omitting the package name (go build) on Linux.
https://github.com/golang/go/issues/24310
A new debian policy restricts the use of fPIC compiled static libraries,
which is (apparently) required by cgo. libax25 in Debian Stretch is
built without fPIC, so we can't use it anymore.
I've included a function in make.bash that downloads and compiles
libax25 to use when building the static Pat binary. Users can use the
env variable CGO_LDFLAGS to specify a custom libax25.a path.
