Building Hugo with the latest version of Chroma

tips & tricks
1

Hello all,

I thought this might be useful to any non-Go developer who wants to build Hugo from master branch, including the latest version of Chroma too (assuming that the heads of both branches are compatible with each other).

hugo_update.sh

Doing hugo version will then print:

Hugo Static Site Generator v0.30-DEV-A354D130:CHROMA-33F604C8 linux/amd64 BuildDate: 2017-09-27T10:25:05-04:00

The script works great, but I’d like to know if there’s a way to optimize this piece in there:

# Tue Sep 26 11:28:47 EDT 2017 - kmodi
# Turns out that the chroma package contains sub-packages too.. so have to
# include all separately.
govendor fetch github.com/alecthomas/chroma
govendor fetch github.com/alecthomas/chroma/formatters
govendor fetch github.com/alecthomas/chroma/formatters/html
govendor fetch github.com/alecthomas/chroma/lexers
govendor fetch github.com/alecthomas/chroma/styles
2

If you have a working Go environment, just delete the vendored package.

go get -u github.com/alecthomas/chroma/...
cd $GOPATH/src/github.com/gohugoio/hugo
make vendor
rm -rf vendor/github.com/alecthomas/chroma
3

I don’t need make vendor as I am doing govendor sync, right?

4

Thanks for that suggestion… I have updated the above gist with that… looks like I didn’t need make vendor as I am doing govendor sync. Let me know if I am overlooking something by doing that.