Linux vs Windows (part 2)
Linux vs Windows (part 2)
Winget sucks ass. Fails half of the time, lists way too much I did not install through Winget m, even had apps broken because of bad updates through Winget.
Never had these problems with scoop or chocolatey though.
lists way too much I did not install through Winget
That’s one of the features though. You can update apps via Winget even if you didn’t originally install them via Winget.
somepackage requires otherpackage version >10.1.79 otherpackage is already at latest version
Have fun compiling it yourself and messing up what is managed by the package manager and what’s not. And don’t forget that the update might break some other package along the way
If your distro maintainer’s do a good job, that situation never happen’s.
Or just use gentoo where that problem doensn’t exist at all.
Most of the time you can just download a release and place the binary in path (or a symlink).
Compiling it yourself should not ‘messing up’ anything, it should build locally:
./configure make -j$(nproc)Now it’s just built, nothing on your system has changed. make install will place requisite files where they need to go, but this generally configurable via prefix or equivalent. You may need to install dependencies, but that’s usually a simple exercise in reading the output from the configuration step.
Compiling software is easy as fuck and is incredibly flexible.
Besides a kernel update… Which one?
Honest question, as I usually just restart to be sure I haven’t missed to restart a service or something, but theoretically I could restart every program and service, that got updated.
Maybe Mint is very conservative here…
Ah yeah, mostly kernel module updates go along with a kernel update. But you are right, yeah.
Although, should be possible to just reload the module and restart X/Wayland, no?
Kde neon made me reboot Everytime it updated. Turns out there was a setting I could disable. Afterwards I was never bugged about rebooting.
Used discover for updates
Maybe you have such a setting?
Not necessarily, you can use kexec
Been running endeavouros for over a year on two machines. The only time I couldn’t boot was when the Nvidia drivers decided not to work with the LTS kernel anymore. So I just started the normal kernel and changed that to the default in my boot manager. This is the only issue I’ve had with it and it’s arch based. I really don’t understand the bad reputation.
Also the arch wiki is applicable to most distros with only slight changes.
I tried installing rust which required some Visual Studio compiler on a Windows machine configured to reset itself when rebooted. It decided I needed a reboot. I’m glad I didn’t have unsaved files…
Needless to say I could not run my program on that machine. Why does it need a reboot? I don’t know. It’s just meant to be a compiler.
Windows is not getting better,
CoPilot, Recall, all more unwanted spyware…
UniGetUI is a good way to maintain software on Windows in a Linux fashion through package managers,
however that does not change that the underlying OS is pure spyware.
Chocolatey is the best option I’ve found for this on Windows:
Chocolatey was created by Rob Reynolds in 2011 with the simple goal of offering a universal package manager for Windows. Chocolatey is an open source project that provides developers and admins alike a better way to manage Windows software.
You can install & uninstall software from the command line and update everything installed through it with one command.
It’s not a real package manager of course. It can’t update the operating system, and Windows applications aren’t built for modularity and shared libraries the way Linux applications are. But it does automate application management like nothing else. I highly recommend this if you use Windows.
Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Chocolatey integrates w/SCCM, Puppet, Chef, etc. Chocolatey is trusted by businesses to manage software deployments.