On 18 May 2018 at 19:01, Oliver Grawert <[email protected]> wrote: > well, my subtle hint would point to simply add it to /etc/environment > here, which would globally cover for everything, would allow us to drop > the profile.d snippet in ubuntu images/installs and to my knowledge > would even be used by systemd (or am i wrong here ?) ... > > (and i think it would even work for zsh) >
Sorry, I do not have time for subtle hints. As you are well aware, snapd cannot modify /etc/environment; (not owned by it, it is freeform text, can contain anything, may or may not have PATH setting, not-upgradable, so on and so forth) said file is not used by systemd; it would not cover things globally; and specifically it would not cover things across other distributions. There are reasons why integration snippet was shipped by snapd in profile.d, and all of those reasons still stand. And more-over the ethos for snapd packaging is to integrate into as many systems as possible, in a native way. Shipping appropriate system-environment-generators will achieve that not only on Ubuntu classic installs but on any systemd-based Linux distros too, which my understanding is the scope for the snapd project. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
