As mentioned here:
After snapd deb installation one has to source /etc/profile.d/apps-bin-path.sh to update PATH for the current shell. exec*(2) system calls make it apparent as to why environment variables can’t be easily updated from an external process such as a package installer but not every user knows about that.
Can we document the process more explicitly somewhere for the first installation of snapd on Ubuntu Server?
it should rather say to log out and back in again instead of sourcing the file …
Any explicit instructions would do.
Right now if you are on a server system (old or new) or on an upgraded desktop (not sure if snapd is installed on do-release-upgrade) you have to face this problem.
Small details tamper adoption because 3-step instructions suddenly don’t work for some people (this is a feedback from a user who installed a fresh server system to try OpenStack via conjure-up).
By the way, the lack of snapd is not the case for images here http://releases.ubuntu.com/16.04.3/ubuntu-16.04.3-server-amd64.iso - only for images downloaded from http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/current
Is there any reason why?