oh, also: # As of 2.19.0, chroma requires WASM build along with other static Javascript # files. Here is an example how to do it with tinygo: # TINYGOROOT=~/tinygo tinygo build -no-debug -target wasm \ # -o cmd/chromad/static/chroma.wasm cmd/libchromawasm/main.go && # chmod -x cmd/chromad/static/chroma.wasm # cp ~/tinygo/targets/wasm_exec.js cmd/chromad/static/
# ftp https://github.com/alecthomas/chroma/archive/refs/tags/v{$V}.tar.gz # tar xvvzf v{$V}.tar.gz # cd chroma-{$V}/cmd/chroma/ && go mod vendor # cd ../chromad/ && go mod vendor # cd .. && mkdir -p /tmp/chroma-{$V}/cmd # cp -r chroma chromad /tmp/chroma-{$V}/cmd/ # cd /tmp/ && tar -cvvf chroma-{$V}.tar chroma-{$V} # gzip -9vo chroma-{$V}.tar.gz chroma-{$V}.tar it would be helpful to add a maintainer target to do this, rather than copy-and-paste. this is typically done as a "dist:" target, see e.g. git-lfs for an example of another port doing this for go software.
