** Also affects: snap-confine (Ubuntu)
** Changed in: snap-confine (Ubuntu)
Status: New => Fix Released
** Also affects: snap-confine (Ubuntu Xenial)
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
Make /snap a build-time configuration option
Status in Snappy Launcher:
Status in snap-confine package in Ubuntu:
Status in snap-confine source package in Xenial:
snap-confine now has a build-time option to re-locate the /snap
directory to an arbitrary location. This allows distributors to put
the /snap directory, for example, to /var/lib/snapd/snap without
affecting any applications at runtime. Snap application see a
consistent world where /snap is still the mount point.
Since this doesn't use this new build-time feature a simple regression
test of running any snap application is sufficient to verify this.
This change does not affect the Ubuntu package.
* This bug is a part of a major SRU that brings snap-confine in Ubuntu
16.04 in line with the current upstream release 1.0.41.
* snap-confine is technically an integral part of snapd which has an
SRU exception and is allowed to introduce new features and take
advantage of accelerated procedure. For more information see
== # Pre-SRU bug description follows # ==
To support cases where the distribution wishes to use another snap
mount directory (other than /snap) snap-confine needs to be aware of
it to locate the core snap.
This should be a build-time option as this is robust and easy to
implement. We can explore other ideas later.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp