Default GIMME_TMP to /tmp/gimme-$USER

[meatballhat]

and exclude it from backups as with GIMME_VERSION_PREFIX.

Closes #7

[tianon]

My only concern with moving this out of /tmp is that we then become responsible for cleaning it out ourselves (where /tmp is generally expected to be cleaned out by the OS if we accidentally forget to), so we need to be slightly more careful about what we put in there and whether it's growing over time. 😅

[meatballhat]

@tianon Very true! Given this solution vs., say, /tmp/gimme-of-$(whoami) (inspired by pytest?), which do you favor? (Or something else?)

[tianon]

$ git grep -n GIMME_TMP gimme
gimme:34:#+               GIMME_TMP - temp directory (default '${GIMME_TMP}')
gimme:347:      cat >"${GIMME_TMP}/test.go" <<'EOF'
gimme:354:      "${1}/bin/go" run "${GIMME_TMP}/test.go"
gimme:455:      local bin_tgz="${GIMME_TMP}/go${version}.${GIMME_OS}.${arch}.tar.gz"
gimme:472:      local src_tgz="${GIMME_TMP}/go${GIMME_GO_VERSION}.src.tar.gz"
gimme:547:      local dlfile="${GIMME_TMP}/known-dl"
gimme:801:: "${GIMME_TMP:=${TMPDIR:-/tmp}/gimme}"

Looking at these uses, test.go is going to be small and consistently overwritten, as is known-dl, and the go tarballs will probably be either used or reattempted, so I guess it probably doesn't make much difference.

Given we don't keep the tarballs (ie, mv $GIMME_TMP/go...tar.gz $GIMMIE_SOMEWHERE_ELSE), I don't see a strong benefit to them living inside our directory (where we do get good benefit from them being in /tmp), so I'd still personally lean towards the existing ${TMPDIR:-/tmp} as our base directory (and fixing the issue-at-hand with something like ${USER:-$(id -u)} injected), but I don't feel so strongly that I'd block any approach others feel is more correct. 👍

[tianon]

TLDR: I'd prefer something like : "${USER:=$(id -u)}" and ${TMPDIR:-/tmp}/gimme-$USER, but don't feel so strongly to block anything

[meatballhat]

@tianon I like your idea better!