Cannot build multiple ROCKs from the same repo with local source
Metadata
Current evaluation
Request to restore `rockcraft pack <part-name>` or provide an alternative for building multiple ROCKs from a single local source. Maintainer acknowledged the accidental removal and apologized.
Suggested action: keep open
Reason: A maintainer explicitly acknowledged the accidental removal of `pack <part-name>` and apologized, confirming the reported workflow is valid and not a misuse. The issue should remain open to track a design discussion or implementation of a supported alternative for multi-part local builds.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
15
Complexity:
50
Confidence:
85
Actionability:
65
Issue body
### Bug Description
Before (v1.4.0), I had a single `rockcraft.yaml` with two parts (one for each server binary written in Golang that I need to pack), and I could call `rockcraft pack my-part-name` to get different ROCKs. I see that option was removed now in `v1.5.2`.
But I still can't pass alternative `rockcraft.yaml` files to `rockcraft pack`: it always picks the one from the current working dir. Moving the `rockcraft.yaml` to a subdir is not an option, because I need the entire root folder to be sent as context to compile both sub-projects. BTW, I use the following source:
```
source-type: local
source: .
```
This is a common pattern in Golang applications: have the same repository from which many different binaries can be built.
This was previously discussed here, without a conclusion: https://matrix.to/#/!NPPCseDHKRvSBMUEXN:ubuntu.com/$F8APWD_OPK64KsECe4MNFQbX1ObhES2aMFKrMN6BRpc?via=ubuntu.com&via=matrix.org
Am I doing something wrong, or is this a real limitation?
For now, I guess I will work around this with symbolic links and scripts.
### To Reproduce
N/A
### Environment
rockcraft v1.5.2 on Ubuntu 22.04.
### rockcraft.yaml
N/A
### Relevant log output
N/A
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
45
Quick Win:
15
Complexity:
50
Confidence:
85
Actionability:
65
|
keep open | Request to restore `rockcraft pack <part-name>` or provide an alternative for building multiple ROCKs from a single local source. Maintainer acknowledged the accidental removal and apologized. | |
| stealth/space-bunny-alpha |
Impact:
50
Quick Win:
12
Complexity:
62
Confidence:
89
Actionability:
62
|
keep open | Rockcraft 1.5.2 cannot select a pack part or alternate manifest while retaining the repository root as local source context; a maintainer said part-name support was removed unintentionally. | |
| qwen/qwen3.6-35b-a3b |
Impact:
35
Quick Win:
12
Complexity:
45
Confidence:
75
Actionability:
60
|
keep open | User cannot build multiple ROCKs from same repo with local source after pack <part-name> was removed in v1.5.2. Maintainer acknowledged removal was a mistake. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18
Staleness:
85
Complexity:
55
Confidence:
70
Support Request:
40
|
keep open | Request to build multiple ROCKs from one repo with local source by passing alternative rockcraft.yaml files to rockcraft pack; maintainer confirmed the removed part-name behavior was unintended and no file option exists. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close not a bug | Request to restore rockcraft pack part-name for building multiple ROCKs from a single repo. Maintainer confirmed the feature was intentionally removed in v1.5.2 due to architectural concerns. Inactive for ~2 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
75
|
close not a bug | Rockcraft v1.5.2 removed pack part-name functionality, preventing building multiple ROCKs from a single repo with local sources. Maintainer confirmed removal was intentional due to Pebble integration concerns. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
45
Confidence:
88
Support Request:
75
|
close not a bug | User reports missing rockcraft pack part-name functionality removed in v1.5.2. Maintainer confirms removal was intentional due to Pebble integration issues, confirming this is expected behavior rather than a bug. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.