If there are any configuration changes that are recommended to make using the software you just installed easier, Scoop will tell you. Scoop will go out, grab all of the dependencies for Git, and install it ready-to-go on your PATH. Just type the following, for example: scoop install git Installing software from Scoop’s repository is simple. The Scoop-recommended level of RemoteSigned is satisfactory for my needs, but I encourage you to read up on execution policies before making that decision for yourself. Getting started with Scoop involves a one-liner in PowerShell: iex (new-object net.webclient).downloadstring('')Īs I mentioned before, if you haven’t done so already, you’ll need to make a small configuration change-and the above one-liner will tell you how. This allows it to run without ever asking for administrator permissions, much as Homebrew does. The key difference between Scoop and Chocolatey that made me a Scoop fan was the fact that, by default, it installs all its packages into a scoop directory right off your user folder. In fact, Homebrew was one of Scoop’s inspirations-and it shows, with a one-command installation (two if you need to make a small Windows config change) that gets you 100% set up. While Scoop can fetch and install packages from the internet to get you up and running with the open-source tools you need, it feels a lot more like the venerable Homebrew.
This time around, I went looking for alternatives and found Scoop.
In the past, I had been using a tool called Chocolatey-something I’d learned about when working with Windows developers on a Web project-but I found its need to always have elevated privileges annoying and unnecessary. Windows development with open-source tools has always been challenging, starting with getting the right tools in place. On a recent project, I needed to bring our source tree over to a Windows system in order to do some testing and light development there.
0 kommentar(er)
