You are correct that this PATH behavior is expected and that sudo -i/sudo -s is preferred (I am trying to get out of this bad habbit myself already), but
My main point is more that this is likely to be a noticeable point of friction -- same with cron. If we consider snappy a first class citizen for installations, it is likely to be confusing that the tools are not in any of the standard paths - even /usr/local.
There is perhaps not a super ideal solution to this situation.. but I think it is worth thinking about.
Side note: the standard path set does include /usr/local, and /usr/games. It's only the profile.d stuff which isn't executed (which is expected). Standard path set appears to be /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
You are correct that this PATH behavior is expected and that sudo -i/sudo -s is preferred (I am trying to get out of this bad habbit myself already), but
My main point is more that this is likely to be a noticeable point of friction -- same with cron. If we consider snappy a first class citizen for installations, it is likely to be confusing that the tools are not in any of the standard paths - even /usr/local.
There is perhaps not a super ideal solution to this situation.. but I think it is worth thinking about.
Side note: the standard path set does include /usr/local, and /usr/games. It's only the profile.d stuff which isn't executed (which is expected). Standard path set appears to be /usr/local/ sbin:/usr/ local/bin: /usr/sbin: /usr/bin: /sbin:/ bin:/usr/ games:/ usr/local/ games