Catkin plugin: Staging area not suitable for building other parts
Bug #1663385 reported by
Kyle Fazzari
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
High
|
Kyle Fazzari | ||
Bug Description
The recommended method of building a snap that will consume content (in this case, libs) from another snap using the content interface is to tar up the producer's staging area and use it as a part to build the consumer.
However, such a workflow doesn't work when the producer's staging area came from the Catkin plugin, as many parts of its environment (cmake files and python scripts) are pointing to its old installdir.
After finishing a build, the Catkin plugin should ensure that what it's produced is usable from the staging area.
| Changed in snapcraft: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Kyle Fazzari (kyrofa) |
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #1 |
| Changed in snapcraft: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #2 |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix here: https:/