lf-lang / lf-lang/installation
WSL/Windows/Git Bash/Cygwin confusion
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Some issues in the current scripts:
- WSL is Linux. If running this script under WSL, it should be the same as running on any other Linux distro, like Ubuntu. It makes people confused to mix reference to WSL and Windows.
https://github.com/lf-lang/installation/blob/819ce99ce1ac459250217c91e5e37b71898df6a5/install.sh#L53-L54
(We are installing Windows, not WSL tools; powershell is cross-platform, but used extensively on Windows; however here we are using bash ) windows-lateston GH Actions uses Git bash as bash. Git bash has$OSTYPE=msys- There is another famous Unix-like environment on Windows, Cygwin, with
$OSTYPE=cygwin. We don't support it at all. lfcuses powershell on Windows. The current way of creating bash script will simply fail under powershell.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with install.sh around lines 53-54, then trace how the scripts are invoked by lfc on Windows and by the windows-latest GitHub Actions runner. Compare the stated WSL, Git Bash, Cygwin, and PowerShell cases; done means the supported environments are distinguished consistently and the bash-script approach no longer fails under the described Windows flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, powershell, shell
- Domain
- devops, operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100