Repository navigation
feat: block installation on Cygwin - #99
chloe41427[bot] wants to merge 1 commit into
Conversation
Cygwin is unsupported due to path-handling incompatibilities with the native SDKMAN components, which surface as confusing failures (empty 'sdk list java', broken 'sdk selfupdate', platform detection falling back to 'exotic'). Detect Cygwin at install time via the existing $cygwin flag (set from uname by os.scala.txt) and exit early with a clear message pointing users to WSL2. Closes #75
|
@claude please review |
|
Claude finished @marc0der's task in 19s —— View job Review of PR #99: block installation on Cygwin
SummaryI don't think this PR is needed, and I'd recommend against merging it as is. Master already blocks Cygwin installs. Main finding: duplicate of an existing guard
With this PR, the install script would contain two Cygwin guards:
The new block can never be reached on Cygwin, because the earlier check exits first. It's dead code, and it adds a second message to keep in sync with the first. Please check whether #75 is already satisfied by the existing include. If it is, close this PR. If #75 is about something the existing guard misses, say what in the issue and fix Minor points
VerdictRequest changes. Drop the duplicate guard, or explain what gap in |
|
Closing this - Claude's review is right: If a real gap in the existing |
What
Blocks SDKMAN installation on Cygwin, as requested in #75.
Cygwin is unsupported: its path handling is incompatible with the native SDKMAN components, which surfaces as confusing failures for users — empty
sdk list java, brokensdk selfupdate, and platform detection falling back toexotic.How
app/views/includes/sanity.scala.txt: added a guard at the top of the sanity checks that bails out early when Cygwin is detected, with a clear message pointing users to WSL2. This reuses the existing$cygwinflag, whichos.scala.txtalready sets fromuname(CYGWIN*).@includes.os()runs before@includes.sanity()in the install template, so the flag is available.features/installation.feature: added a scenario asserting the rendered install script contains the Cygwin guard and message.Acceptance criteria (from #75)
CYGWIN*via the existinguname-based$cygwinflag)$cygwin == true)Notes
sdkman-ansible, so it needs an ansible deploy after merge.Closes #75