Which package manager do you use on windows and why? What don't you like about the others?
I've used them all extensively, but I'll be keeping my thoughts on them to myself.
Which one doesn't shit up your system with a trillion files scattered everywhere every time it installs something?
>>105855762That would be not chocolatey. Scoop seemed ok in that regard. Haven't tried winget.
I have like 5 programs I use, why would I need a 6th to manage them.
>>105855629 (OP)Those are not "package managers". These are just front ends for wannabe wintoddlers who don't want to double click on installer executables so they use cli program to do it for them.
Real package managers don't run executables, they just extract package which is basically an archive maybe executing some scripts afterwards. They keep database of all installed files and resolve dependencies. They provide file database for packages in repository so you can find which package hosts desired file.
>>105855798>ERM ACKSHULLYYou arenโt welcome here lintroon.
Why hasn't anyone ported pacman to windows? I'll fucking do it and setup a repo too.
>>105855798That's literally what scoop does. It will even unpack MSIs with stuff like lessmsi.
winget is just windows store and runs the MSIXs which are no different from interpreting an rpm or deb.
>>105856442You think I don't know about msys2 or cygwin? It's a unix compat layer for windows, it's not the same.
Tryhard solution for most. You get older version of an .exe
Choco packages are prepared by stinky pajeet hands, it's literally safer to download all your software from rutracker than using Choco.
Winget simply provides download links to developer's website, latest GitHub release or microshit Store, and then downloads the installer, showing the link to the user.
Winget updates are awkward
>upgrade winrar
>* no such package, please use FULL PACKAGE NAME *
>upgrade alexanderrorschachkx.winrar.com.google.org
>works
>>105855629 (OP)Someone once suggested choco for batch installing vcredists, so I did just that and kept it afterwards. Don't use it much, but it's alright.
>>105855629 (OP)winget because it's the MS supported one.
>>105855629 (OP)I use scoop as the main and fallback to winget if something isn't available on it. I like the former and don't like the latter. I don't use chocolatey since it doesn't offer anything better than the 2 others.
>>105855798Like
>>105856434 said. Scoop is the real package manager, while Winget is just a CLI frontend to Winstore.
>>105855629 (OP)i use chocolatei gui as a program installer and updater
>>105856434>>105856510thinking about migrating to scoop. sounds really good.
Does it have most of the packages chocolatey and winget have?
can I run a script to schedule the auto update?
>>105855629 (OP)Scoop is the best. Winget was alright. Choco was complete garbage.
>>105855629 (OP)>>105855762scoop. scoop is the only one that performs like a package manager. the others are just really bad automation scripts for running normal install wizards unmodified.
just use all of them within a pajeetware GUI like a sophisticated man
https://github.com/marticliment/UniGetUI
>>105855629 (OP)The only reason I used scoop was to install sudo and now it comes stock with windows so I don't even need to install scoop anymore, I barely use chocolatey because installers glitch up more often than not. Winget wins.
>>105855629 (OP)for me it's scoop. by far.
>>105855629 (OP)I prefer portable programs I can unzip into a folder and not worry about them fucking up anything in the system.
>>105855629 (OP)None, because they are yet another way to lure user into heavy cloud dependence. I archive all the relevant software and driver installers locally on external drives. I refuse to bend the knee to the cloud jew and their poo golems.
bump65 is the best windows package manager
>>105861854scoop keeps a cache of the zips you dunce
scoop is only good because the msi(x) installers are opaque as hell because of how dogshit the tooling is. It's like someone wanted something like content addressed files like ostree, but fucked it up because it was the 90s and they ran out of time to ship. msiexec is also the absolute worst fucking interface to the "package manager" to ever be made, given it will block if you fail to give it arguments it won't tell you about and also conveniently background forks (or however the fuck that shit works in windows) if you run it in a WinRM, powershell or cmd with a console host that you can interact with, which means multiple calls to msiexec can race if you don't do stupid shit to prevent the backgrounding.
Obviously msi wasn't good enough because you couldn't specify dependencies on other msi's like you could in deb's and rpm's, so that's when msix came about. I suppose it's better than nothing, but the tooling is still pure dogshit.
In scoop, you take the expected behavior of how Windows linker works, dump it in a folder, have a script do post install stuff like setting some environment variables or registry keys, create some insane "shim" executable because linker facial abuse and you just hope for the best. It works out ok, but honestly it still sucks asshole. I'd just swallow the winget pill if your shitty wageslave job doesn't disable the windows store (they did anyway because your cyber security team is retarded) and if you're not a wage slave using windows, what the fuck are you doing with your life?
>>105855629 (OP)Scoop and itโs not even close.
>>105855798This is not true for scoop at least. It allows for multiple versions to be installed side by side per user if you wish. Winget is just a CLI for downloading and installing msixโs