Currently if a bundle is used on a machine with an existing julia installation, the JULIA_DEPOT_PATH may point to that existing installation instead of the bundle. This means users of the shipped binary have to set the depot path manually with an environment variable which adds significant friction, and may cause unpredictable behavior (e.g. wrong Artifact usage).
I am not actually sure if this is possible without changes to julia itself as I think the JULIA_DEPOT_PATH expansion only works on absolute paths in the end, but it would be useful to make bundles self contained.
Currently if a bundle is used on a machine with an existing julia installation, the
JULIA_DEPOT_PATHmay point to that existing installation instead of the bundle. This means users of the shipped binary have to set the depot path manually with an environment variable which adds significant friction, and may cause unpredictable behavior (e.g. wrong Artifact usage).I am not actually sure if this is possible without changes to julia itself as I think the
JULIA_DEPOT_PATHexpansion only works on absolute paths in the end, but it would be useful to make bundles self contained.