Installing something on arch is easy imo. The CLI is simple and well enough documented, and the package build system is easy to use. For comparison with ubuntu: pacman -S name is not harder than apt install name. And try to install something on ubuntu if it’s not in the official package repos.
ubuntu: pacman -S name is not harder than apt install name.
Eh, it’s a teensy bit harder, since you have to remember what -S means, rather than the easy to remember and plain English ‘install’. But, yeah, not much of a difference.
And try to install something on ubuntu if it’s not in the official package repos.
1: Go to that something’s website.
2: look for their download/install instructions page, scroll to Linux instructions if necessary.
3: Install instructions for Debian/Ubuntu are usually the first one listed, and typically just consist of a few commands you can copy and paste over without modifying.
4: those commands were written for previous version of Ubuntu and now dependency tree doesn’t compute, also one of the commands is to add their custom repo, and you don’t have keys for it so it doesn’t work anyway. You try to remove the bad repo and now your apt is all fucked. You regenerate your repo list, googled the package and your version name, random stackexchage page gave you their live repo, but it needs a newer version of a library that incompatible with 54 of something that you already have. You learn about snap, installed 43Gb of something, it exists but still doesn’t really work because package maintaiers didn’t actually move it to snap, it was someone else. By this point you copy-pasted so many commands into your terminal you afraid it gained sentience. You call your more computer literate friend, he starts saying something about incompatible dependancies, containers, and you don’t really understand much. By the end, you decide that you didn’t actually want the software.
Later you discover that your sound doesn’t work anymore, and there is an error when you reboot.
Installing something on arch is easy imo. The CLI is simple and well enough documented, and the package build system is easy to use. For comparison with ubuntu:
pacman -S nameis not harder thanapt install name. And try to install something on ubuntu if it’s not in the official package repos.Eh, it’s a teensy bit harder, since you have to remember what -S means, rather than the easy to remember and plain English ‘install’. But, yeah, not much of a difference.
1: Go to that something’s website.
2: look for their download/install instructions page, scroll to Linux instructions if necessary.
3: Install instructions for Debian/Ubuntu are usually the first one listed, and typically just consist of a few commands you can copy and paste over without modifying.
It isn’t particularly difficult in most cases.
4: those commands were written for previous version of Ubuntu and now dependency tree doesn’t compute, also one of the commands is to add their custom repo, and you don’t have keys for it so it doesn’t work anyway. You try to remove the bad repo and now your apt is all fucked. You regenerate your repo list, googled the package and your version name, random stackexchage page gave you their live repo, but it needs a newer version of a library that incompatible with 54 of something that you already have. You learn about snap, installed 43Gb of something, it exists but still doesn’t really work because package maintaiers didn’t actually move it to snap, it was someone else. By this point you copy-pasted so many commands into your terminal you afraid it gained sentience. You call your more computer literate friend, he starts saying something about incompatible dependancies, containers, and you don’t really understand much. By the end, you decide that you didn’t actually want the software.
Later you discover that your sound doesn’t work anymore, and there is an error when you reboot.