tar-content plugin should allow setting a prefix
Bug #1478055 reported by
Michael Terry
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
The tar-content plugin should let the user set a directory/prefix under which to expand the content.
You don't always want all the little toplevel files like README to clutter the snap toplevel (or collide).
This is very similar to the floated idea of having a generic prefix key for any part. But while that is being discussed, the tar-content plugin has special urgency for it (since it doesn't have a separate install step that puts files in expected places). We might consider implementing prefix for just it for now.
| Changed in snapcraft: | |
| status: | New → Opinion |
Revision history for this message
| Chad Miller (cmiller) wrote | #1 |
| Changed in snapcraft: | |
| status: | Opinion → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in snapcraft: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
I think this is fixed with the "destination" parameter.