/snap/bin not in $PATH on desktop

Mark Shuttleworth mark at ubuntu.com
Sun Sep 11 21:35:35 UTC 2016


On 09/09/16 14:25, Jamie Strandboge wrote:
> Since snaps aren't expected to be able to launch programs from
> /snap/bin for the
> reasons already mentioned, I would argue that snapd should strip /snap/bin from
> the PATH for launched commands to avoid confusion. checkbox and things that
> launch other snaps' commands via devmode are the outliers and it seems perfectly
> reasonable to me for them to add /snap/bin to their PATH via wrappers.

Jamie, I disagree with the blanket statement that 'snaps aren't expected
to'...

We have interfaces specifically to offer snaps the ability to do
anything. Whether a snap is *allowed* to use an interface is a different
question. But if by definition snaps are just packages, and packages are
software that might do anything, then snaps must at least in principle
be able to do anything.

For example, a chef snap should definitely be able to do what Sylvain is
asking, on Classic Ubuntu.

Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20160911/6ed9d83b/attachment.sig>


More information about the Snapcraft mailing list