other day and whose updates will down your production once a week as a host?
Interresting approach, not gonna lie
Will down? Why should? Updates are needed and updates mostly require rebooting services. Missing updates is not an enhancement
"Update requires manual intervention" goes brrr
That means nothing, just to replace a file or ask for confirmation about overwrite
Or really? https://archlinux.org/news/xorg-cleanup-requires-manual-intervention/
Oh no, I have to uninstall a package in two years, what impossible task
Well keep doing distro devs' job if you like it 🤷🏻♂ btw it happens much more often.
Only for soname clashing, the majority are overwrite some files and it happens only some times per year
I'm not saying it's impossible to manage that. I'm saying you shouldn't have to.
Those lib names clashes are what made me lose money because some asshat though using arch for servers was a nice idea
Do you think it would be a difficult task to put that removal in the pre installation script? The reason is ONLY for keeping the user at the center of the system
You can keep user in control by asking what the user wants when they execute "pacman -Syu". And by providing default resolution that will be used on --noconfirm for automated upgrades.
May I ask what your business is? :)
Oh no, having to read a webpage twice per year is terrible
It was some SaaS doing accounting
I repeat: you shouldn't have to.
You shouldn't fear to be able to manage your system either
Was it a FOSS solution by any chance?
No, it was not
I don't fear. But I also use systems that are better designed :)
oh ok, I wasn't aware you were using Windows
If you can't completely automate the upgrade process and provide sane defaults then your system is not relevant for real-world production servers.
If I wanted to have to manage the 170 packages my software uses one by one and update them as painfully as possibly envisionable while checking the documentation for any fatal api changes that could put my application down and ruining the day of several companies, I would use gentoo
The only way for avoid this is not to update them API breakage is made from the software author, not from the distribution. So if you need a system whose packages are not updated to the latest version, you should not use Arch in the first place
Guess what? most distributions stay at the same major version of a software until the next distro release, but not rolling releases
It is the distribution's job to make sure all packages from official repos work correctly with each other.
you described what rolling means LOL
Rolling means you will have to do dependency management everyday for anything even mildly complex
Обсуждают сегодня