I asked a question on Ask Ubuntu about how to make snaps depend on each other, which it seems is not possible. The only answer so far referred me to using aliases. However I cannot get them to work.
I’ve modified the example in the first post I referred to as follows:
I’ve updated the snap using
snapcraft and I’ve installed it using the
--devmode --dangerous flags, but I don’t see any of these commands being automatically aliased. Am I missing something?
I’m not sure aliases solve the reference problems, it depends how things are invoked, usually snap commands should invoke each other using internal names, the external commands/names are not always available.
That post about aliases is out-of-date as well, this has information about more recent changes/workings: Improving the aliases implementation
should invoke each other using internal names
So in the example I referred to, the
server should be able to see the
bar application by just invoking it with
server cannot spawn
bar, I get a “permission denied” error.
I don’t remember what’s the status quo, it’s likely that /snap/bin is in the PATH but is not useful internally because of the access issues you mentioned. Not sure what’s the intention here. Somebody else can chime in on that.
I just saw that I cannot execute
bar manualy because of a permission denied problem. I’m downloading the zip file of the application to see if the command referred in my
snapcraft.yaml configuration does not have the right permissions…
I’m downloading the zip file of the application to see if the command referred in my snapcraft.yaml configuration does not have the right permissions…
No it doesn’t The other problem ahead I see is that the executable contains some shared libraries packaged with it, and I’m not sure how or if
snap handles that: