Unable to create an app that runs an executable found in another snap via content-sharing
Bug #1654665 reported by
Kyle Fazzari
This bug report is a duplicate of:
Bug #1666013: Snapcraft reports an error if the executable for a command is provided by a content interface.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm building a ROS system trying to use the content sharing interface to hold the base libraries and tools (such as roslaunch). Then in a consumer snap, I try to export an app using a binary contained in the ros-base snap (roslaunch, specifically) and of course when priming the consumer snap I get:
The specified command 'roslaunch' defined in the app 'launch-project' does not exist or is not executable
I'm able to work around this by shipping a wrapper to do the roslaunch call, but perhaps we could make that experience better.
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #1 |
To post a comment you must log in.
This bug existed first, but the one that duplicated it is better.