Setting MISE_DATA_DIR only works for absolute paths

[davidkuridza]

I am not sure whether I missed something in the documentation or whether I'm doing something wrong, but it seems MISE_DATA_DIR cannot be a relative path.

Steps to reproduce:

1. Create a new directory, e.g. /tmp/mise, and move into it:

❯ mkdir -p /tmp/mise && cd /tmp/mise

2. Install a package using a relative path, e.g. .foo:

❯ MISE_DATA_DIR=.foo mise use --pin go
mise ERROR failed to install core:[email protected]
mise ERROR No such file or directory (os error 2) at path "/private/tmp/mise/.foo/downloads/go/1.23.6/.foo/downloads/go/1.23.6/go1.23.6.darwin-arm64.tar.gzIaaRJz"
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

3. Install a package using the absolute path, e.g. /tmp/mise/.foo:

❯ MISE_DATA_DIR=/tmp/mise/.foo mise use --pin go
mise [email protected] ✓ installed                                                                                                                                                                                       mise /private/tmp/mise/mise.toml tools: [email protected]

The same behaviour is observed by setting MISE_DATA_DIR in .env or mise.toml directly.

Is this a bug, or is there some other way to use a directory inside the current path?

[roele]

I think none of the global directory environment variables supports relative paths (kinda defeats the purpose of a global store in context of cd hooks i suppose). With command/variable substitution something like MISE_DATA_DIR=$(pwd)/.foo mise use go probably works.

[davidkuridza]

MISE_DATA_DIR=$(pwd)/.foo mise use go works, however, it needs to be used exactly in this way. mise doesn't evaluate it if it's set in mise.toml or .env for example. One solution would be having the path hardcoded in an .env file (excluded from version control), another for mise to handle relative paths.

If we use mise for python in at least two places, then python freeze reports the package from both places. This might be a python only issue which could be resolved within mise, but there's also a case where one might want to have all mise dependencies checked into the repository.

[roele]

For the mise.toml use case you could use templates but these do not work with .env files though.

[env]
MISE_DATA_DIR = "{{ exec(command='pwd') }}/.foo"

[davidkuridza]

Thank you very much, exactly what I need. Also, TIL about the templates, thanks!