Most applications “resolve” current, even snapd when setting up the environment:
sergiusens@umbar:~$ snap run --shell beets.beet
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
sergiusens@umbar:/home/sergiusens$ echo $HOME
sergiusens@umbar:/home/sergiusens$ echo $SNAP
That is my personal pain point as I have to navigate code that writes configuration so that the configuration writing logic is snap aware.
For the case of cmake, it causes things like this (as seen from the cmake configuration logs):
ignore line: [/usr/bin/c++ -v -o CMakeFiles/cmTC_170b6.dir/CMakeCXXCompilerABI.cpp.o -c /snap/cmake/513/share/cmake-3.18/Modules/CMakeCXXCompilerABI.cpp]
And I am not sure why, cmake eventually resolves to its real self:
ignore line: [/snap/cmake/513/bin/cmake -E cmake_link_script CMakeFiles/cmTC_170b6.dir/link.txt --verbose=1]
If the concern is that updates would affect AppArmor profiles and current, I would also like for the “do not update underneath me while running” to also get some attention