Symlink to snapcraft apps no longer working
zygmunt.krynicki at canonical.com
Mon Nov 14 09:41:31 UTC 2016
> Wiadomość napisana przez Martin Winter <mwinter at opensourcerouting.org> w dniu 11.11.2016, o godz. 10:54:
> Not sure when this (recently) changed.
> All apps as defined by a snap are prefixed with the snap name
> Ie, I have under apps a “vtysh” defined, which then ends up as
> quagga.vtysh (for the quagga snap).
> So far no issue.
> Now, a few weeks/months back, I was able to create a symlink
> with “vtysh” pointing to “quagga.vtysh” and then could use the same
> simple “vtysh” command to call the app. (same as traditional package installs)
I think this is related to snap-run. You may have noticed that the quagga.vtysh itself is a symlink to /usr/bin/snap. The new „snap run” command understands symlinks and uses this as a hint on what to run.
> Link had to be done outside snap, but it allowed to keep all scripts
> At the current snapd version (2.16ubuntu3), this does no longer work.
> all apps ends up as a symlink to the same /usr/bin/snap binary and somehow the
> binary seems to fail to call the correct app if there is another symlink
> Is there a way to get symlinks to still work as before?
> - Martin
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
More information about the Snapcraft