Public bug reported:


the snap naming scheme to rename executables to  snapname.appname can
severely break functionality.

I just had the problem that ubuntu's packages for the rust language
compiler are outdated and don't compile recent code, and therefore
created my first snap to pack the distributed compiler and tools suite
into a snap (see ). The rust
compiler+tools and snap would perfectly match each other, since rust is
rather system independent, and it would work just perfectly as a snap,
but the renaming scheme causes trouble since tools don't find each

I then found several discussions about the aliasing of apps, snap
aliases and the aliases: clause in snapcraft.yaml, but found the
automatic way in snapcraft.yaml to be not working. It is included in
meta/snap.yaml, but ignored and still requires a manual alias command.

This is currently somewhat annoying since it is currently unclear and
not documented about how to get around that naming scheme in a clean and
user-comprehensible way.

It currently looks as if aliases need to be set manually, but I don't
see how to tell users that they have to do it and how after installing
the snap.


ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: snapd 2.27.5+17.04
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 20 10:08:17 2017
InstallationDate: Installed on 2016-04-22 (545 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: snapd
UpgradeStatus: Upgraded to zesty on 2017-04-18 (184 days ago)

** Affects: snapd (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-bug zesty

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  snap's naming scheme for executables breaks functionality and state of
  aliases is unclear

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to