Create a Scoop manifest for Clojure's CLI tools on Windows
Description
Scoop is kind of like Homebrew-for-Windows. It fetches packages and installs them in a portable way, puts binaries/shims on your Windows path, etc. There are a few options like this for Windows, but I have found Scoop to be the simplest and most effective for developer-style tools (and that is in fact a focus of Scoop, per their FAQ).
I have created a Scoop manifest for the Clojure CLI tools and it seems to work quite well. The clj and clojure tools show up in both cmd.exe and in PowerShell, and in cmd.exe they bypass the PowerShell execution warnings.
There are a number of options here if the team would be interested in maintaining a Scoop manifest for the Clojure CLI tools:
Add the Scoop app manifest to the clojure/brew-install repo and tell people to scoop install RAWGITHUBLINK directly from there.
I like the first option, especially since Leiningen is already in Scoop using that option.
I have attached the current version of my Scoop app manifest for the Clojure CLI tools to this ticket. This manifest is also available in a GitHub Gist, so if you install Scoop then you can run the following command to try out the Clojure CLI manifest:
I have not done this work yet, but it might be worthwhile to add autoupdate support to the app manifest if you choose to go with the first option. That should be as simple as using the "github" variant of Scoop's "checkver" feature, if the goal is to tie releases of the app manifest to the latest GitHub release.
Thanks for all of the hard work on making these tools run on Windows, I very much appreciate the effort!
Environment
Windows
Attachments
1
Activity
Show:
Sean Corfield September 19, 2019 at 2:31 AM
Iād forgotten about this ticket. I added the following to the clj-on-Windows page in the t.d.a. wiki:
Scoop is another option that people seem to like ā see as an example of how it could be packaged for Scoop (that depends on this wiki page existing and containing the latest version number for the Powershell installer!).
Scoop is kind of like Homebrew-for-Windows. It fetches packages and installs them in a portable way, puts binaries/shims on your Windows path, etc. There are a few options like this for Windows, but I have found Scoop to be the simplest and most effective for developer-style tools (and that is in fact a focus of Scoop, per their FAQ).
I have created a Scoop manifest for the Clojure CLI tools and it seems to work quite well. The
cljandclojuretools show up in bothcmd.exeand in PowerShell, and incmd.exethey bypass the PowerShell execution warnings.There are a number of options here if the team would be interested in maintaining a Scoop manifest for the Clojure CLI tools:
Submit the app manifest to the official Scoop repo.
Add the Scoop app manifest to the clojure/brew-install repo and tell people to
scoop install RAWGITHUBLINKdirectly from there.I like the first option, especially since Leiningen is already in Scoop using that option.
I have attached the current version of my Scoop app manifest for the Clojure CLI tools to this ticket. This manifest is also available in a GitHub Gist, so if you install Scoop then you can run the following command to try out the Clojure CLI manifest:
I have not done this work yet, but it might be worthwhile to add autoupdate support to the app manifest if you choose to go with the first option. That should be as simple as using the "github" variant of Scoop's "checkver" feature, if the goal is to tie releases of the app manifest to the latest GitHub release.
Thanks for all of the hard work on making these tools run on Windows, I very much appreciate the effort!