Snapcraft reports an error if the executable for a command is provided by a content interface

[James Henstridge]

I tried to create a snap with the following definitions in my snapcraft.yaml

    plugs:
      python3:
        interface: content
        content: python3
        target: python
        default-provider: python36-jamesh

    apps:
      hello:
        command: python/bin/python3 $SNAP/hello.py
        plugs:
          - python3

The idea being that the executable for the command would be provided by another snap via the content interface. Unfortunately, Snapcraft refuses to build my snap because the executable doesn't exist in the snap.

I can work around this by creating a shell script that exec's the program shared via the interface, but it would be nice if I didn't have to work around this check.

Perhaps it would make sense to suppress the error if the executable's path is below a directory that will act as a mount point for the content interface?

[Sergio Schvezov (sergiusens)]

Can this be solved by doing

`command: /usr/bin/env $SNAP/python/bin/python3 $SNAP/hello.py`

[Kyle Fazzari (kyrofa)]

Even if that works, it only solves this issue for python commands.

[Launchpad Janitor (janitor)]

[Expired for Snapcraft because there has been no activity for 60 days.]