docs/snapcraft-syntax.md should explicitly name the conditions under which a file is expected to end up in stage/ and snap/
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without action due to inactivity. The documentation request to clarify stage-packages and snap directive behavior was abandoned. No updates or fixes were implemented.
Suggested action: —
No scores available.
Issue body
https://github.com/ubuntu-core/snapcraft/blob/master/docs/snapcraft-syntax.md currently says:
- stage-packages (list of strings) A list of Ubuntu packages to use that would support the part creation.
This is vague and leaves unclear, under which conditions files from these packages (or their dependencies) can be expected into end in the final snap (that they _can_ end up in snap somehow is implied by the different description of build-packages explicitly denying that for those).
E.g. having
stage-packages:
- libxml2-dev
snap:
- usr/lib/x86_64-linux-gnu/*
- usr/include/libxml2/*
results in neither of:
usr/include/libxml2/libxml/parser.h
usr/lib/x86_64-linux-gnu/libxml2.so
to end up in the snap, while only the second ends up in the stage/ dir. (on snapcraft 2.2.2/xenial)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without action due to inactivity. The documentation request to clarify stage-packages and snap directive behavior was abandoned. No updates or fixes were implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The documentation request clarifying stage-packages file placement was abandoned due to prolonged inactivity, with no updates provided to the snapcraft-syntax.md file. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Documentation request clarifying stage-packages behavior was closed without changes, likely abandoned due to inactivity and superseded by updated Snapcraft guides. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1642446 Better documentation for stage-packages and build-packages | snapcraft (launchpad) | closed | Request to document stage-packages and build-packages in snapcraft help plugins closed without resolution or comments, indicating abandonment. | |
| #1805214 stage-snaps | snapcraft (launchpad) | closed | Closed without comments or resolution. The request to stage snap contents like packages was abandoned due to prolonged inactivity. | |
| #1536659 docs/snapcraft-syntax.md doesn't discuss build-packages | snapcraft (launchpad) | closed | Abandoned and closed without resolution, leaving the build-packages documentation gap unaddressed. The maintainer noted existing CLI help covers the topic, but no markdown updates were implemented. | |
| #1607249 docs/snapcraft-syntax.md should refer to source related syntax | snapcraft (launchpad) | closed | Abandoned and closed as outdated by maintainer @mr-cal. No documentation updates were implemented. | |
| #1605164 Errors due to "missing" files using "stage:" | snapcraft (launchpad) | closed | Abandoned. Reported a snapcraft staging error when excluding directories with missing files. Closed without comments or a fix, indicating the issue was stale. | |
| #1538688 Support referencing the stage dir from snapcraft.yaml | snapcraft (launchpad) | closed | Feature request to introduce a SNAPCRAFT_STAGE environment variable for referencing the stage directory. Closed without implementation or discussion, effectively abandoned due to age and lack of maintainer engagement. |