Found this when building the uaa image.

cloudfoundry-incubator/uaa-cli redirects to cloudfoundry/uaa-cli, but using marman to download the first will result in a json file, not the release artifact.

Today I learnt (or realised something i knew but haven't been applying):

This is a file target

build/marman-linux: $(SRC) deps
	GOARCH=amd64 GOOS=linux go build -o build/marman-linux -ldflags ${LDFLAGS} ./cmd/marman/main.go

This is a pseudo-target

build-darwin: build/marman-darwin

If you want make to be efficient, try to make sure that file targets always depend on other file targets

In the build/marman-linux target, we're depending on a pseudo-target, deps which means the go build will always be run again, despite there being nothing to do.

the fix is to move deps to the pseudo target:

build/marman-linux: $(SRC)
	GOARCH=amd64 GOOS=linux go build -o build/marman-linux -ldflags ${LDFLAGS} ./cmd/marman/main.go

build-darwin: deps build/marman-darwin

OR we can establish a file target for deps using the temp/tags trick but that's not always feasable.

This isn't an immediate issue, in that building our go apps is pretty fast, but it can balloon out and cause friction when later you decide to add a slower pre-processing action to your builds.