jochen
e1f5d4fdf0
The controller imports mesh-host/validate through a replace onto the forge that holds it, and every build — the build agent's go build in a fresh toolchain container, the Dockerfile's go mod download — would have fetched it through the public proxy and checksum database at build time: a merge breaking main on the network, the class Phase 1 removes. vendor/ is committed; go builds from it with nothing fetched, and refuses to build when it and go.mod disagree, so a pin moved without go mod vendor fails at once. The Dockerfile copies vendor/ and builds with GOPROXY=off.
26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
The .words file is used by gospel (v1.2+), which wraps the Hunspell libraries
|
|
but populates the dictionary with identifiers from the Go source.
|
|
|
|
<https://github.com/kortschak/gospel>
|
|
|
|
Alas, no comments are allowed in the .words file and newer versions of gospel
|
|
error out on seeing them. This is really a hunspell restriction.
|
|
|
|
We assume en_US hunspell dictionaries are installed and used.
|
|
The /AFFIXRULES are defined in en_US.aff (eg: /usr/share/hunspell/en_US.aff)
|
|
Invoke `hunspell -D` to see the actual locations.
|
|
|
|
Words which are in the base dictionary can't have extra affix rules added to
|
|
them, so we have to start with the affixed variant we want to add.
|
|
Thus `creds` rather than `cred/S` and so on.
|
|
|
|
So we can't use receive/DRSZGBU, adding 'U', to allow unreceive and variants,
|
|
we have to use unreceive as the stem.
|
|
|
|
We can't define our own affix or compound rules,
|
|
to capture rfc\d{3,} or 0x[0-9A-Fa-f]{2}
|
|
|
|
The spelling tokenizer doesn't take "permessage-deflate" as allowing for ...
|
|
"permessage-deflate", which is an RFC7692 registered extension for websockets.
|
|
We have to explicitly list "permessage".
|