Warn when unexpected things are in the snap dir

Bug #1791368 reported by Kyle Fazzari on 2018-09-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Status tracked in Trunk
Legacy
High
Kyle Fazzari
Trunk
High
Kyle Fazzari

Bug Description

Snapcraft expects that the snap/ directory only contains its own things: plugins, hooks, metadata, etc. This is also the directory it writes state files. Putting other things in there has never been supported, but the snapcraft CLI has never warned about using it this in this way. It needs to start.

Kyle Fazzari (kyrofa) wrote :
Changed in snapcraft:
status: New → Incomplete
status: Incomplete → In Progress
importance: Undecided → High
assignee: nobody → Kyle Fazzari (kyrofa)
Kyle Fazzari (kyrofa) on 2018-09-11
Changed in snapcraft:
milestone: none → 2.44
Changed in snapcraft:
status: In Progress → Fix Committed
Adam Collard (adam-collard) wrote :

FWIW, I think this is going to be ineffective.

If I have a software project that I then snap, and need to have snap specific bits for (e.g. bash completion, patches to upstream etc.) my natural inclination will be to put it in the snap/ directory. The same way that debian/ works, and any other packaging system for that matter.

With snapcraft claiming ownership of snap/ it doesn't give me a place to put these files.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers