1. 7
  1.  

  2. 2

    I have tried scoop and it didn’t feel good enough for me.

    • The “repo” uses https://raw.github.com links, and github ratelimit has kicked in when I was setting up my machine for example.
    • I did not find it well discoverable (eg. when having to enable repos manually)
    • the “portable apps” installed cannot be fully trusted in my opinion.
    • the whole thing has the same trust issues as chocolatey in my opinion, without proper background institution and processes it cannot be trusted as well as a major linux distribution for example.

    Overall I have tried it, but I’ll stick to the scripts I have authored and manual installation on the few times I need to set up something on windows.

    1. 1

      If it’s just yet another setup.exe downloader, and not a real package manager, then why should I care?

      1. 5

        You probably wouldn’t, but that’s also not what it is; it is indeed a real package manager, albeit still a relatively simple one à la Homebrew. The GitHub repo honestly actually provides a better overview than the official homepage, but as a quick summary, Scoop:

        • Installs in the user directory, so you don’t need to deal with UAC pop-ups;
        • Handles dependencies;
        • Handles upgrades and updates;
        • When it does have to work with a setup.exe for whatever reason, avoids you having to deal with it by extracting and setting things up behind-the-scenes; and
        • Is trivially extensible

        Some of the above is admittedly cultural (the team prefers finding and sourcing portable apps whenever possible), but some is also unique to Scoop’s implementation. For what it’s worth, I’ve submitted at least one new formula to Scoop and updated a few from time to time, and found the process really simple; the feel is similar to Homebrew, in a good way, and makes it feel significantly lighter-weight than something like Chocolatey.

        1. 1

          Installs in the user directory, so you don’t need to deal with UAC pop-ups

          When I was on Vista, you would’ve sold me with that one line.

          1. 1

            Ah, that’s potentially damn handy. Thanks for that bit of info.

            If that’s the case it should work on my Windows VM I use to get access to my corporate overlord’s network on my own hardware :)

        2. 1

          Tried installing it on a Windows 7 machine in my lab a week or two ago. I had to install the latest Powershell, and then I found out that there’s a bug in that Powershell that prevents scoop from installing packages…

          On my Windows 10 machine it works fine though

          1. [Comment from banned user removed]

            1. 2

              I’m not sure what you’re looking at, but those are very different. Scoop is a competitor to Chocolatey; Cmder is a competitor to cmd.exe.

              1. 1

                Yeah but the video showed packages all readily available in cmder. That’s all.

              2. 1

                I’m super confused at this too. cmder is a console/shell like thing, not a package manager.

                1. 1

                  I understand but it seemed to show only packages that are already available in cmder.

                  1. 1

                    Either you are confused or cmder has capabilities that I am not aware of, in which case, spill it so I can figure this out! :)

                    Looking at the Github repository for cmder it appears the developers don’t integrate a package manager (I didn’t think they did.)

                    is it possible your local sysadmin or something bundled chocolatey or scoop by default with your installation of cmder?

                2. 0

                  Excuse me?

                Stories with similar links:

                1. Scoop - a command line installer for Windows via jdarnold 3 years ago | 5 points | 5 comments