Support referencing sibling directories of project root
Metadata
Current evaluation
Request to allow referencing sibling directories outside the project root during builds, potentially via a new project-root key, currently triaged and under discussion regarding implementation details.
Suggested action: keep open
Reason: The issue is triaged, actively discussed by maintainers and users, and outlines clear implementation paths for a significant feature request. Recent activity confirms it is being tracked and considered for implementation.
Staleness:
35
Complexity:
65
Confidence:
90
Support Request:
0
Issue body
### Check existing issues
- [x] I've verified that this request isn't described by any existing issues.
### Request
Consider the following directory structure:
```
my-repo/
shared-lib/
...
charm-1/
charmcraft.yaml
...
charm-2/
charmcraft.yaml
...
```
Currently, Charmcraft cannot readily build the individual charms without some preprocessing, because the `shared-lib` directory will not be accessible from the build containers for each of the charms.
Instead of using the folder containing charmcraft.yaml as the project root, the build environment should mount the entire containing repository and then set the working directory to the charmcraft.yaml directory. Each charm could then define a part with `source: ../shared-lib`.
### The problem it solves
This would fix the limitations encountered in e.g. https://github.com/canonical/charmcraft/issues/1079 and https://github.com/canonical/rockcraft/issues/959.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| 2026-06-15 12:31:27.494408+00:00 | qwen3.6-35b-a3b-mtp-q6 |
Staleness:
35
Complexity:
65
Confidence:
90
Support Request:
0
|
keep open | Request to allow referencing sibling directories outside the project root during builds, potentially via a new project-root key, currently triaged and under discussion regarding implementation details. |
| 2026-06-15 12:28:27.092547+00:00 | pending | — | — | — |