Skip to content

fix: expose kotlinc through feature container environment - #75

Merged
mikaello merged 1 commit into
mainfrom
fix-kotlinc-container-path
Sep 24, 2026
Merged

mikaello merged 1 commit into
mainfrom
fix-kotlinc-container-path

Conversation

@mikaello

@mikaello mikaello commented Sep 24, 2026 •

Copy link
Copy Markdown
Owner

Change

Expose /opt/kotlinc/bin through the Feature's containerEnv.PATH so kotlinc works in interactive and noninteractive processes.
Use ktlint's canonical release URL and keep installer progress messages.
The installer writes only to /opt and /usr/local/bin; its former USERNAME lookup did not affect installation or ownership.

The feature-starter installer confirms that installation runs as root and documents _REMOTE_USER and _CONTAINER_USER for features that need the final user.
This feature does not need those variables.

Validation

  • bash -n src/kotlinc/install.sh test/kotlinc/test.sh
  • jq empty src/kotlinc/devcontainer-feature.json
  • CI exercises the feature on Debian, Ubuntu, and the Dev Containers Ubuntu base image.

Related PRs

PR #67 changes installsAfter from common-utils:1 to :2 in the same metadata file.
I verified that Git combines #67 and this PR cleanly; the result retains both the new containerEnv.PATH and common-utils:2.
They can merge in either order without stacking.
PR #66 changes installer checks that this PR's simpler installer no longer uses.

@mikaello
mikaello force-pushed the fix-kotlinc-container-path branch from cf21580 to 12b7060 Compare September 24, 2026 11:59
@mikaello
mikaello enabled auto-merge (squash) September 24, 2026 11:59
@mikaello
mikaello merged commit 6c90f5a into main Sep 24, 2026
7 checks passed
@mikaello
mikaello deleted the fix-kotlinc-container-path branch September 24, 2026 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant