Windows support with scoop installer without bash
See original GitHub issueI tried to use this from windows. Unfortunately it needs a bash environment. I know that this is the intended purpose for this project.
I created a simple scoop installer but with a jar created from https://github.com/hj-lee/kscript (thanks @hj-lee ).
scoop add bucket raisercostin https://github.com/raisercostin/raiser-scoop-bucket
scoop install kscript
After that I was able to execute scripts with dependencies from windows without any bash help via a simple kscript hello.ks
.
How can I help to have an official release with the merge from @hj-lee fork?
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (3 by maintainers)
Top Results From Across the Web
How to Install Scoop in Windows - MakeUseOf
Open PowerShell. You can do this by searching for PowerShell in the start menu. · Inside PowerShell, type the code below: iwr -useb...
Read more >How to install the Scoop package manager in Windows 10
With Scoop, you can install it by running "scoop install 7zip" from the Command Prompt. Scoop will automatically download and install the latest ......
Read more >Scoop
A command-line installer for Windows. ... Scoop installs programs you know and love, from the command line with a minimal amount of friction....
Read more >How to Install and Use the Scoop Windows Package Manager
Scoop is a command-line installer for Windows that lets you quickly install and update packages without breaking anything.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That can be fixed and I’d recommend moving that conversation to https://github.com/holgerbrandl/kscript/issues/197. If we all agree that next release’s goal is full Windows compatibility we just need some coordination 👍
About @hj-lee I’d really like to see some of its improvements (specially the one “calling directly the kotlin compiler instead of bash”) but I don’t like “use classloader to run the script main and more” (I’ve experienced classpath pollution in gradle plugins that add code to the classpath). Said that, I have to say that some of @hj-lee ideas are great but having many improvements in the same branch puts the leader in a complicated position of “all or nothing”. How about splitting them so we can choose with ones we want merge asap?
Thanks for your clarifying description. Though, I’m not sure how to fix/incorporate that into kscript.