confusing behaviour using the root of the repo as source
Metadata
Current evaluation
Closed without resolution. The discussion on confusing relative path behavior for snapcraft.yaml source directories was abandoned. No code changes were implemented.
Suggested action: —
No scores available.
Issue body
The new default for snapcraft will be to have the snapcraft.yaml in the snap directory.
That seems like a nice feature, and some people don't want to add the yaml to their root, so they will be happy for sure.
However, we have the common practice of using . as the source. Now, the meaning of . is confusing.
Lets say I have my snapcraft project in /home/elopio/project.
If I put the snapcraft.yaml in /home/elopio/project, source: . will mean /home/elopio/project as the source.
If I put the snapcraft.yaml in /home/elopio/project/snap, source: . will still mean /home/elopio/project. I find this slightly confusing.
And there's also a not-so-uncommon practice of putting the snapcraft.yaml in a subdirectory, and run snapcraft from that subdir.
If I put the snapcraft.yaml in /home/elopio/project/packaging, source: .. will mean /home/elopio/project.
If I put the snapcraft.yaml in /home/elopio/project/snap, source: .. will mean /home/elopio, which is wrong.
I'm not really sure what to do about this, or even if we have to do anything about this. I'm open this bug for discussion.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The discussion on confusing relative path behavior for snapcraft.yaml source directories was abandoned. No code changes were implemented. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
85
Support Request:
20
|
close stale | Discussion on confusing relative path resolution for source: . in snapcraft.yaml when placed in subdirectories. Unlabelled, inactive for ~9.5 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
65
|
close stale | Discussion about confusing relative path resolution for the source field in snapcraft.yaml when placed in subdirectories. Unlabelled, inactive for ~9 years, no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Discussion about confusing behavior of relative source paths in snapcraft.yaml when placed in subdirectories. Unlabelled, inactive for ~9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
30
Confidence:
92
Support Request:
20
|
close stale | Relative source paths in snapcraft.yaml resolve to the repository root instead of the yaml directory, causing confusion with the new default nested structure. Open for discussion with no comments or assigned action. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1816397 Modifying snapcraft.yaml with parts using local sources get dirty | snapcraft (launchpad) | closed | Closed without resolution or comments. Appears abandoned, with no fix or workaround implemented. |