Charmcraft build does not let you decide the output directory
Metadata
Current evaluation
Implemented the ability to specify a custom output directory for charmcraft builds. The feature was added to the pack command, resolving the original limitation.
Suggested action: —
No scores available.
Issue body
This might be more of a feature request, but it would be nice to be able to decide where we want the charm to end up. Currently, when running `charmcraft build`, the charm.charm ends up in the same directory. For functional tests, it is desirable to have a build directory where the charm to be tested will be located. I currently work around this by having a Makefile that moves the build charm to the desired location.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Implemented the ability to specify a custom output directory for charmcraft builds. The feature was added to the pack command, resolving the original limitation. | |
| qwen/qwen3.6-35b-a3b | — | — | The feature request to specify a custom output directory for charmcraft builds was resolved by implementing the option in the pack command. The issue was closed following this fix. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to specify a custom output directory for charmcraft builds was fixed. The feature was implemented in the pack command instead of the build command. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Specifying a custom output directory for charmcraft builds is now supported. Resolved by implementing the feature in the pack command. Closed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Specifying a custom output directory for charmcraft builds was fixed by implementing the feature in the pack command. The issue is closed. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #434 Output path changed with charmcraft 1.1.0 | charmcraft | closed | Identified as a regression, the output path change in charmcraft 1.1.0 was fixed. The pack command now correctly outputs to the current directory instead of the project directory. |