[Classic confinement] Robogif - Accessing system binaries from a snap

[jdstrand]

@Mavrik

Now, when attempting to publish the snap, I’ve noticed that I need to use ‘classic’ confinement because my tool wants to run “adb” from the users path. That is because adb loves to run a single global daemon to communicate with the device and that daemon is not tolerant of different adb versions used. So if I package adb inside the snap and user is a developer using adb from Android Studio distribution, the adb invocation will kill users ADB daemon and prevent him from using functionality in Android Studio. The only way to avoid that is to always use the same adb from path.

The problem is that if your snap is classic, there is no guarantee that any adb is on the system. There is an android-studio snap though. It sounds like perhaps it should provide an adb slot that your snap can then plugs. See Interfaces · canonical/snapd Wiki · GitHub for details.