The Scoop wiki has a nice write-up comparing Scoop and Chocolatey. While some of these tools may be available through Chocolatey, the Scoop ecosystem is designed with such tools in mind. Scoop also seems natural for installing command-line tools that you might miss from Unix-like systems, such as Linux or Mac. If you do not have Admin access to your system (for instance, this is a shared server with Remote Desktop access), then Scoop is the right choice. Apps will not by default show in the start menu, and if plugins or addons expect to find the installation in a certain directory (looking at you, OBS Studio!), there will be some inconvenience and tedious setup. By default, it installs packages to ~/scoop/ and this is both a strength and a confusion point. Scoop is designed for developers who have an affinity for Unix. In an Admin-level PowerShell window, the following should work, provided you have set the ExecutionPolicy as above:Įnter fullscreen mode Exit fullscreen mode Scoop: non-Admin by default, installs in user directory The applications will have shortcuts in your start menu, and possibly on your desktop. This application is far more than a tool for tech support people to easily set up PCs. For Windows users, Ninite is arguably the only really safe place to get freeware. In general, installing one of these packages, such as Google Chrome, will require elevated Admin privileges, and will install it where you would expect (likely C:\Program Files\ or C:\Program Files (x86)\). Ninite is a free tool that automatically downloads, installs, and updates various Windows programs for you, skipping past the evil toolbar offers. Chocolatey: conventional install locations, as AdminĬhocolatey can install from a community repository with thousands of packages. This policy will "win" when you are logged in. The second line means that all scripts and configuration files downloaded from the Internet must be signed by a trusted publisher, but scripts you write yourself will work, for the current user. The first line means that all scripts and configuration files on this computer must be signed by a trusted publisher, even if you write them yourself. Enter fullscreen mode Exit fullscreen mode
0 Comments
Leave a Reply. |