Ruby plugin paths are inconsistent
Metadata
Current evaluation
Closed without resolution. An internal Jira ticket (CRAFT-4950) was created to track the inconsistent Ruby plugin paths. No fix or pull request was merged.
Suggested action: —
No scores available.
Issue body
### Bug Description
The Ruby plugin as implemented in #1395 treats paths inconsistently:
1. The install prefix for the interpreter is `$CRAFT_PART_INSTALL/usr`.
2. `GEM_HOME` is `$CRAFT_PART_INSTALL`.
3. `BUNDLE_PATH` is `$CRAFT_PART_INSTALL`.
This means:
1. The ruby executable is in `/usr/bin/`, and system-global gems are in ``/usr/lib/ruby/gems/3.2.0/`.
2. Gem-installed executables are in `/bin`
3. Bundle-installed executables are in `/ruby/<ruby_version>/bin`
Instead, we should set the build environment so that `gem install` and `bundle install` go into the system gem path.
### To Reproduce
N/A
### part yaml
```shell
```
### Relevant log output
```shell
N/A
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. An internal Jira ticket (CRAFT-4950) was created to track the inconsistent Ruby plugin paths. No fix or pull request was merged. | |
| qwen/qwen3.6-35b-a3b | — | — | The issue was closed and synced to Jira ticket CRAFT-4950. No fix or resolution was documented in GitHub, indicating it was tracked externally without a resolved outcome here. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without resolution. Ruby plugin path inconsistency remains unfixed, with tracking moved to internal Jira ticket CRAFT-4950. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. Only an automated Jira sync comment was posted, indicating the report was logged internally but received no follow-up. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1365 Add Ruby Plugin | snapcraft | closed | Adding a Ruby plugin to snapcraft was closed without merging. The contributor fixed a path resolution bug, but pending integration tests and unresolved reviews led to the pull request being abandoned. |