snapcraft run should only run from the project directory
Metadata
Current evaluation
Closed without implementation. The request to restrict snapcraft run to the project directory was abandoned or superseded by later design changes, with no discussion or resolution details provided.
Suggested action: —
No scores available.
Issue body
run seems to be able to work from any localtion, this can be bad for regular users.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request to restrict snapcraft run to the project directory was abandoned or superseded by later design changes, with no discussion or resolution details provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Restricting snapcraft run to the project directory was closed without resolution. Zero comments and no implementation notes indicate the request was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report noted snapcraft run executes from arbitrary directories, creating risks for regular users. Zero comments and no linked pull requests indicate the issue was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1659085 snapcraft needs to migrate to a snap directory | snapcraft (launchpad) | closed | Closed without resolution. The proposed migration of snapcraft to a snap directory, including build artifact relocation and plugin updates, was abandoned or superseded by subsequent architecture changes. | |
| #1597711 snapcraft: self.run() is inconsistent in providing | snapcraft (launchpad) | closed | Inconsistent working directory behavior in snapcraft's self.run() was reported but closed without resolution or comments, indicating the report was abandoned. No fix or documentation update was implemented. | |
| #1626625 snapcraft can't run tests as part of building a snap | snapcraft (launchpad) | closed | Closed without implementation. The request to add test execution rules to snapcraft received no comments and was abandoned or superseded by newer snapcraft testing features. | |
| #1548915 snapcraft without argumens should just snap | snapcraft (launchpad) | closed | Closed without implementation. The feature request to run snapcraft without arguments was abandoned, with no discussion or code changes made. | |
| #1746403 snapcraft fails to find hooks if ran from snap directory. | snapcraft (launchpad) | open | 2017 report: running snapcraft from the snap/ directory builds without error but omits hooks, causing confusing install failures; proposes enforcing project-root CWD. No maintainer activity in 8+ years; likely obsolete after the core22 rewrite. | |
| #1069 snapcraft.yaml and building in snap directory | snapcraft | closed | Closed without merging. The maintainer reviewed the snapcraft.yaml and build directory changes but opted to close the pull request to de-clutter the repository. |