From: Ilya_Shlyakhter Date: Wed, 4 Mar 2020 17:39:02 +0000 (+0000) Subject: added todo: restore original environment when running external special remotes from... X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~104^2~53 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=8f48ebd8c255e27b2b1dc7039a3220179fe86d41;p=git-annex.git added todo: restore original environment when running external special remotes from standalone git-annex? --- diff --git a/doc/todo/restore_original_environment_when_running_external_special_remotes_from_standalone_git-annex__63__.mdwn b/doc/todo/restore_original_environment_when_running_external_special_remotes_from_standalone_git-annex__63__.mdwn new file mode 100644 index 0000000000..46414d84ff --- /dev/null +++ b/doc/todo/restore_original_environment_when_running_external_special_remotes_from_standalone_git-annex__63__.mdwn @@ -0,0 +1,3 @@ +When [[standalone|install/Linux_standalone]] git-annex runs external special remote, it does so in the standalone environment. I wonder if it makes more sense to run them in the original environment (by restoring PATH from ORIG_PATH)? If the external special remote has been packaged with a package manager like conda, it expects its dependencies to come from the environment set up by that package manager, not the git-annex standalone environment. + +Also, maybe rename exported vars like ORIG_PATH to GIT_ANNEX_ORIG_PATH.